On Wed, Nov 9, 2022 at 11:20 AM Patrick Venture <vent...@google.com> wrote:
> Hi all, > > I've been trying to debug qtest problems recently. I have seen the assert > socket failures a bunch now and am digging into why. I've also seen this a > lot and I'm curious if anyone has any ideas: > > ./configure --target-list=aarch64-softmmu,aarch64-linux-user > make -i check-report-qtest-aarch64.junit.xml > > Exception in callback TestHarness._run_tests.<locals>.test_done(<Task > finishe...r directory')>) at > /usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py:1843 > handle: <Handle TestHarness._run_tests.<locals>.test_done(<Task > finishe...r directory')>) at > /usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py:1843> > Traceback (most recent call last): > File "/usr/lib/python3.10/asyncio/events.py", line 80, in _run > self._context.run(self._callback, *self._args) > File > "/usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py", line > 1845, in test_done > f.result() > File > "/usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py", line > 1840, in run_test > res = await test.run(self) > File > "/usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py", line > 1384, in run > await self._run_cmd(harness, cmd) > File > "/usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py", line > 1438, in _run_cmd > p = await self._run_subprocess(cmd + extra_cmd, > File > "/usr/local/google/git/workspaces/qemu_71/meson/mesonbuild/mtest.py", line > 1412, in _run_subprocess > p = await asyncio.create_subprocess_exec(*args, > File "/usr/lib/python3.10/asyncio/subprocess.py", line 218, in > create_subprocess_exec > transport, protocol = await loop.subprocess_exec( > File "/usr/lib/python3.10/asyncio/base_events.py", line 1667, in > subprocess_exec > transport = await self._make_subprocess_transport( > File "/usr/lib/python3.10/asyncio/unix_events.py", line 207, in > _make_subprocess_transport > transp = _UnixSubprocessTransport(self, protocol, args, shell, > File "/usr/lib/python3.10/asyncio/base_subprocess.py", line 36, in > __init__ > self._start(args=args, shell=shell, stdin=stdin, stdout=stdout, > File "/usr/lib/python3.10/asyncio/unix_events.py", line 799, in _start > self._proc = subprocess.Popen( > File "/usr/lib/python3.10/subprocess.py", line 969, in __init__ > self._execute_child(args, executable, preexec_fn, close_fds, > File "/usr/lib/python3.10/subprocess.py", line 1845, in _execute_child > raise child_exception_type(errno_num, err_msg, err_filename) > FileNotFoundError: [Errno 2] No such file or directory: > '/usr/local/google/git/workspaces/qemu_71/build/tests/qtest/arm-cpu-features' > > In the past I've seen it unable to find other qtest files. I'm a bit > stumped as to why this would be flaky about finding the test files it needs. > If the problem is that I didn't run the regular make first. Which it looks like it, since I Just ran the normal "make" and saw: [864/867] Compiling C object tests/qtest/arm-cpu-features.p/arm-cpu-features.c.o [865/867] Linking target tests/qtest/arm-cpu-features I'm going to be sad. I don't know why making the test target wouldn't trigger the thing to be built, but I'm definitely starting to think that's my problem. > > Patrick >
