On Mon, 26 Oct 2020 at 12:48, Christian Schoenebeck <qemu_...@crudebyte.com> wrote: > > On Montag, 26. Oktober 2020 11:33:42 CET Peter Maydell wrote: > > I get a 'make check' failure on x86-64 Linux host: > > > > PASS 54 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/config PASS 55 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/create_dir PASS 56 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/unlinkat_dir PASS 57 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/create_file PASS 58 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/unlinkat_file PASS 59 qtest-x86_64: qos-test > > /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio- > > 9p-tests/local/symlink_file Received response 7 (RLERROR) instead of 73 > > (RMKDIR) > > Rlerror has errno 2 (No such file or directory) > > ** > > ERROR:../../tests/qtest/virtio-9p-test.c:300:v9fs_req_recv: assertion > > failed (hdr.id == id): (7 == 73) > > ERROR qtest-x86_64: qos-test - Bail out! > > ERROR:../../tests/qtest/virtio-9ptest.c:300:v9fs_req_recv: assertion > > failed (hdr.id == id): (7 == 73) > > Makefile.mtest:3953: recipe for target 'run-test-492' failed
I just got this again on an entirely different pullreq so that suggests that this is indeed an intermittent currently in master: PASS 49 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/synth/flush/ignored PASS 50 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/synth/readdir/basic PASS 51 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/synth/readdir/split_512 PASS 52 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/synth/readdir/split_256 PASS 53 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/synth/readdir/split_128 PASS 54 qtest-i386/qos-test /i386/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-9p-pci/virtio-9p/virtio-9p-tests/local/config Received response 7 (RLERROR) instead of 73 (RMKDIR) Rlerror has errno 2 (No such file or directory) ** ERROR:../../tests/qtest/virtio-9p-test.c:296:v9fs_req_recv: assertion failed (hdr.id == id): (7 == 73) ERROR qtest-i386/qos-test - Bail out! ERROR:../../tests/qtest/virtio-9p-test.c:296:v9fs_req_recv: assertion failed (hdr.id == id): (7 == 73) Makefile.mtest:1857: recipe for target 'run-test-230' failed > So the 9p server is already failing to create the test case directory > "./qtest-9p-local/05/" relative to your current working directory. This sounds suspicious, because there's nothing in that filename that's specific to the test case being qtest-i386 and not qtest-something-else. How does the test harness deal with the possibility of the same virtio-9p-pci test being run in parallel for multiple guest architectures under a make -jN setup ? > What puzzles me is that the previous test cases succeeded there, which all > create their own test directory in the same way: > > ./qtest-9p-local/01/ > ./qtest-9p-local/02/ (<-- dir vanishes after that test completed) > ./qtest-9p-local/03/ > ./qtest-9p-local/04/ > ... After the build failed, the qtest-9p-local directory was empty. thanks -- PMM
