Hello everyone, We have been getting inquiries about the status of Avocado on Python 3 quite often. The port has been going on for quite some time, but in the last few months, it has seen a lot more activity.
So, one way we measure the port progress is to run Avocado's test suite on Python 3. Right now[1] all unittests[2] pass, and the functional[3] tests status look like this: test_argument_parsing.py: OK test_basic.py: OK test_export_variables.py: OK test_gdb.py: OK test_job_timeout.py: OK test_journal.py: OK test_loader.py: OK test_lv_utils.py: OK test_output.py: OK test_plugin_diff.py: OK test_plugin_jobscripts.py: OK test_replay_basic.py: OK test_replay_external_runner.py: OK test_replay_failfast.py: OK test_skiptests.py: OK test_standalone.py: OK test_statuses.py: OK test_streams.py: OK test_sysinfo.py: OK test_teststmpdir.py: OK test_thirdparty_bugs.py: OK test_unittest_compat.py: OK test_utils.py: OK test_wrapper.py: OK test_getdata.py: 1 pending issue: problem identified as variant IDs change on Python 3 (due to hashing decoded strings, that is, bytes) test_interrupt.py: 2 pending issues: test_badly_behaved_sigterm and test_well_behaved_sigterm (AssertionError: Avocado was still running after receiving SIGINT twice.) test_output_check.py: 2 pending issues: test_output_record_and_check_combined, test_output_tamper_combined We're trying very hard to have this on the upcoming release (59.0), so stay tuned, and if possible, join the code review and testing process on the related PRs. [1] - Meaning code in master and proposed pull requests [2] - https://github.com/avocado-framework/avocado/tree/master/selftests/unit [3] - https://github.com/avocado-framework/avocado/tree/master/selftests/functional -- Cleber Rosa [ Sr Software Engineer - Virtualization Team - Red Hat ] [ Avocado Test Framework - avocado-framework.github.io ] [ 7ABB 96EB 8B46 B94D 5E0F E9BB 657E 8D33 A5F2 09F3 ]
