Il mar 16 lug 2024, 18:45 John Snow <js...@redhat.com> ha scritto:
> My only ask is that we keep the tests running in the custom venv
> environment we set up at build time
>
Yes, they do, however pytest should also be added to pythondeps.toml if we
go this way.
If we move to pytest, it's possible we can eliminate that funkiness, which
> would be a win.
>
There is the pycotap dependency to produce TAP from pytest, but that's
probably something small enough to be vendored. And also it depends on what
the dependencies would be for the assets framework.
I'm also not so sure about recreating all of the framework that pulls vm
> images on demand, that sounds like it'd be a lot of work, but maybe I'm
> wrong about that.
>
Yep, that's the part that I am a bit more doubtful about.
Paolo
Tacit ACK from me on this project in general, provided we are still using
> the configure venv.
>
>
>> Thomas
>>
>>
>> Ani Sinha (1):
>> tests/pytest: add pytest to the meson build system
>>
>> Thomas Huth (7):
>> tests/pytest: Add base classes for the upcoming pytest-based tests
>> tests/pytest: Convert some simple avocado tests into pytests
>> tests/pytest: Convert info_usernet and version test with small
>> adjustments
>> tests_pytest: Implement fetch_asset() method for downloading assets
>> tests/pytest: Convert some tests that download files via fetch_asset()
>> tests/pytest: Add a function for extracting files from an archive
>> tests/pytest: Convert avocado test that needed avocado.utils.archive
>>
>> tests/Makefile.include | 4 +-
>> tests/meson.build | 1 +
>> tests/pytest/meson.build | 74 ++++
>> tests/pytest/qemu_pytest/__init__.py | 362 ++++++++++++++++++
>> tests/pytest/qemu_pytest/utils.py | 21 +
>> .../test_arm_canona1100.py} | 16 +-
>> .../test_cpu_queries.py} | 2 +-
>> .../test_empty_cpu_model.py} | 2 +-
>> .../test_info_usernet.py} | 6 +-
>> .../test_machine_arm_n8x0.py} | 20 +-
>> .../test_machine_avr6.py} | 7 +-
>> .../test_machine_loongarch.py} | 11 +-
>> .../test_machine_mips_loongson3v.py} | 19 +-
>> .../test_mem_addr_space.py} | 3 +-
>> .../test_ppc_bamboo.py} | 18 +-
>> .../version.py => pytest/test_version.py} | 8 +-
>> .../test_virtio_version.py} | 2 +-
>> 17 files changed, 502 insertions(+), 74 deletions(-)
>> create mode 100644 tests/pytest/meson.build
>> create mode 100644 tests/pytest/qemu_pytest/__init__.py
>> create mode 100644 tests/pytest/qemu_pytest/utils.py
>> rename tests/{avocado/machine_arm_canona1100.py =>
>> pytest/test_arm_canona1100.py} (74%)
>> rename tests/{avocado/cpu_queries.py => pytest/test_cpu_queries.py} (96%)
>> rename tests/{avocado/empty_cpu_model.py =>
>> pytest/test_empty_cpu_model.py} (94%)
>> rename tests/{avocado/info_usernet.py => pytest/test_info_usernet.py}
>> (91%)
>> rename tests/{avocado/machine_arm_n8x0.py =>
>> pytest/test_machine_arm_n8x0.py} (71%)
>> rename tests/{avocado/machine_avr6.py => pytest/test_machine_avr6.py}
>> (91%)
>> rename tests/{avocado/machine_loongarch.py =>
>> pytest/test_machine_loongarch.py} (89%)
>> rename tests/{avocado/machine_mips_loongson3v.py =>
>> pytest/test_machine_mips_loongson3v.py} (59%)
>> rename tests/{avocado/mem-addr-space-check.py =>
>> pytest/test_mem_addr_space.py} (99%)
>> rename tests/{avocado/ppc_bamboo.py => pytest/test_ppc_bamboo.py} (75%)
>> rename tests/{avocado/version.py => pytest/test_version.py} (82%)
>> rename tests/{avocado/virtio_version.py =>
>> pytest/test_virtio_version.py} (99%)
>>
>> --
>> 2.45.2
>>
>>
>>
