Date: Tue, 27 Aug 2024 21:22:29 +0000 From: bugzilla-noreply@freebsd.org To: testing@FreeBSD.org Subject: [Bug 281100] fusefs tests silently skip themselves Message-ID: <bug-281100-32464-XdVKApMkOX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281100-32464@https.bugs.freebsd.org/bugzilla/> References: <bug-281100-32464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281100 --- Comment #2 from Alan Somers <asomers@FreeBSD.org> --- The problem is in the googletest-ATF integration. If you do "kyua debug access:main", you'll see that each individual test case is indeed SKIPPED. = But that information isn't communicated to ATF. And since multiple googletest = test cases correspond to each ATF test case, it's not clear what we should do. = What if some googletest test cases are skipped but others aren't? I'll dig into the code and see if we can skip the entire thing if fusefs is= n't loaded. That should be easy, and it's the most common cause for these test= s to get skipped. In the meantime, I'll look at the gtest-tap-listener. BTW, what I do when I want to run a single test case is: $ cd /usr/tests/sys/fs/fusefs $ sudo mkdir mountpoint $ sudo chmod 1777 mountpoint $ sudo chflags uchg mountpoint $ ./access -v --gtest_filter=3DAccess.unlink_sticky_directory Note: Google Test filter =3D Access.unlink_sticky_directory [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] Running 1 test from 1 test suite. [----------] Global test environment set-up. [----------] 1 test from Access [ RUN ] Access.unlink_sticky_directory INIT ino=3D 0 ACCESS ino=3D 1 mask=3D0x1 LOOKUP ino=3D 1 some_file.txt UNLINK ino=3D 1 [ OK ] Access.unlink_sticky_directory (1 ms) [----------] 1 test from Access (1 ms total) [----------] Global test environment tear-down [=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D] 1 test from 1 test suite ran. (1 ms total) [ PASSED ] 1 test. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281100-32464-XdVKApMkOX>