Both of them usually failed with: /usr/src/tests/sys/aio/aio_test.c:934: open failed: No such file or directory sys.aio.aio_test.vectored_unaligned: https://ci.freebsd.org/job/FreeBSD-main-amd64-test/19367/ https://ci.freebsd.org/job/FreeBSD-main-amd64-test/19324/ https://ci.freebsd.org/job/FreeBSD-stable-13-amd64-test/782/ https://ci.freebsd.org/job/FreeBSD-stable-13-amd64-test/759/ sys.aio.aio_test.vectored_zvol_poll: https://ci.freebsd.org/job/FreeBSD-main-amd64-test/19361/ https://ci.freebsd.org/job/FreeBSD-main-amd64-test/19325/ https://ci.freebsd.org/job/FreeBSD-main-aarch64-test/383/ https://ci.freebsd.org/job/FreeBSD-main-aarch64-test/374/ https://ci.freebsd.org/job/FreeBSD-stable-13-amd64-test/762/ https://ci.freebsd.org/job/FreeBSD-stable-13-amd64-test/759/
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=0b159faaca08e6cc89abcd29b4b1360f97e18245 commit 0b159faaca08e6cc89abcd29b4b1360f97e18245 Author: Li-Wen Hsu <lwhsu@FreeBSD.org> AuthorDate: 2021-09-28 19:32:47 +0000 Commit: Li-Wen Hsu <lwhsu@FreeBSD.org> CommitDate: 2021-09-28 19:32:47 +0000 Temporarily skip flaky tset cases under sys.aio.aio_test in CI - sys.aio.aio_test.vectored_unaligned - sys.aio.aio_test.vectored_zvol_poll PR: 258766 Sponsored by: The FreeBSD Foundation tests/sys/aio/aio_test.c | 5 +++++ 1 file changed, 5 insertions(+)
A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=095d3f98fb3d907fbd2e5c799bb2988532e9bf63 commit 095d3f98fb3d907fbd2e5c799bb2988532e9bf63 Author: Li-Wen Hsu <lwhsu@FreeBSD.org> AuthorDate: 2021-09-28 19:32:47 +0000 Commit: Li-Wen Hsu <lwhsu@FreeBSD.org> CommitDate: 2021-09-29 19:38:35 +0000 Temporarily skip flaky tset cases under sys.aio.aio_test in CI - sys.aio.aio_test.vectored_unaligned - sys.aio.aio_test.vectored_zvol_poll PR: 258766 Sponsored by: The FreeBSD Foundation (cherry picked from commit 0b159faaca08e6cc89abcd29b4b1360f97e18245) tests/sys/aio/aio_test.c | 5 +++++ 1 file changed, 5 insertions(+)
It looks like the problem may be related to the fact that openzfs creates the zvol character device asynchronously. So it's possible that the device file doesn't exist immediately after the zpool command returns.