On Tuesday, 30 June 2026 09:28:48 CEST Pierrick Bouvier wrote:
> Hi Christian,
Hi Pierrick,
> This series brought a test regression:
> $ ./build/pyvenv/bin/meson test -C build \
> --setup thorough --print-errorlogs \
> qemu:qtest-aarch64/qos-test
> ...
> ERROR:../tests/qtest/libqos/virtio-9p-client.c:280:v9fs_req_recv:
> assertion failed (hdr.id == id): (7 == 121)
>
> It seems to come test added in patch 19
> "tests/9p: add 3 xattr FID limit test cases (synth fs driver)"
> This test runs only with slow setup, so I suspect it never worked and
> was never ran.
Of course I ran these slow tests.
I intentionally registered these tests as "slow" tests as they take a long
time to complete and QEMU tests being notorious on exceeding the overall CI
timeout limit. So these tests are exempted from running in the official CI
pipeline, but not from mine.
I just reran them with latest master head. However I am unable to reproduce
your reported test error so far.
You cropped the output too aggressively. I need to know:
- Which test exactly failed? (especially whether it's really a synth backend
or a local backend test that failed)
- What is the errno being printed *before* the "assertion failed" message?
("(hdr.id == id): (7 == 121)" just means 9p server responded with an error
response instead of the expected one)
- Were you running the tests in a Docker environment or something or just
plain locally?
- Does the underlying host file system support xattrs? (might matter if it's a
local backend test that's failing)
/Christian
