Thomas Huth <th...@redhat.com> writes: > On 17/07/2025 10.42, Alex Bennée wrote: >> Manos Pitsidianakis <manos.pitsidiana...@linaro.org> writes: >> >>> Add argument parsing to functional tests to improve developer experience >>> when running individual tests. All logs are printed to stdout >>> interspersed with TAP output. >>> >>> ./pyvenv/bin/python3 ../tests/functional/test_aarch64_virt.py --help >>> usage: test_aarch64_virt [-h] [-d] >> Am I holding it wrong? >> ➜ ./pyvenv/bin/python >> ../../tests/functional/test_aarch64_virt.py --help >> Traceback (most recent call last): >> File >> "/home/alex/lsrc/qemu.git/builds/all/../../tests/functional/test_aarch64_virt.py", >> line 16, in <module> >> from qemu_test import QemuSystemTest, Asset, >> exec_command_and_wait_for_pattern >> File "/home/alex/lsrc/qemu.git/tests/functional/qemu_test/__init__.py", >> line 14, in <module> >> from .testcase import QemuBaseTest, QemuUserTest, QemuSystemTest >> File "/home/alex/lsrc/qemu.git/tests/functional/qemu_test/testcase.py", >> line 26, in <module> >> from qemu.machine import QEMUMachine >> ModuleNotFoundError: No module named 'qemu' >> I thought the point of the venv is we had all the modules we need >> automatically available to the PYTHONPATH? > > The "qemu" module is special since we ship it in our repository. See > the "PYTHONPATH" description in docs/devel/testing/functional.rst.
Is there anyway to setup the venv so it automatically does that? -- Alex Bennée Virtualisation Tech Lead @ Linaro
