From: Gustavo Romero <gustavo.romero@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, thuth@redhat.com, qemu-arm@nongnu.org,
1844144@gmail.com
Subject: Re: [PATCH 2/4] tests/functional: Support tests that require a runner
Date: Tue, 26 Aug 2025 12:20:29 -0300 [thread overview]
Message-ID: <ff89f821-e0aa-4a4e-9ac9-f50a6ee062af@linaro.org> (raw)
In-Reply-To: <87bjo32vmf.fsf@draig.linaro.org>
Hi Alex,
On 8/25/25 13:50, Alex Bennée wrote:
> Gustavo Romero <gustavo.romero@linaro.org> writes:
>
>> Add support for running tests that require a specific runner.
>>
>> The test is specified via a tuple (name, runner, protocol), where name
>> is the test name as found in the tests/functional directory without the
>> 'test_' prefix and the .py extension, runner is an array containing the
>> runner and any arguments required by the runner, and protocol is
>> the test protocol used by Meson to determine whether the test passed or
>> failed.
>>
>> The test tuples are added to arrays that follow the current naming
>> logic but with the suffix '_with_runner' appended to their names. In
>> Meson it's not easy to select an element in an array at runtime based on
>> its type, so it's simpler to have a new array for these new test types
>> than use the current ones from the tests that don't require a runner,
>> and so avoid mixing strings and tuples in the same array.
>>
>> Currently there is only one runner, the GDB runner, but more runners can
>> be defined and associated to a test via the tuple.
>>
>> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
>> ---
>> meson.build | 4 +++
>> tests/functional/meson.build | 62 ++++++++++++++++++++++++++++++++++++
>> 2 files changed, 66 insertions(+)
>>
>> diff --git a/meson.build b/meson.build
>> index 50c774a195..8d482f0809 100644
>> --- a/meson.build
>> +++ b/meson.build
>> @@ -75,6 +75,10 @@ have_user = have_linux_user or have_bsd_user
>>
>> sh = find_program('sh')
>> python = import('python').find_installation()
>> +# Meson python.get_path() on 'purelib' or 'platlib' doesn't properly return the
>> +# site-packages dir in pyvenv, so it is built manually.
>> +python_ver = python.language_version()
>> +python_site_packages = meson.build_root() / 'pyvenv/lib/python' + python_ver / 'site-packages'
>>
>> cc = meson.get_compiler('c')
>> all_languages = ['c']
>> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
>> index 311c6f1806..1f70b70fd4 100644
>> --- a/tests/functional/meson.build
>> +++ b/tests/functional/meson.build
>> @@ -349,6 +349,23 @@ tests_xtensa_system_thorough = [
>> 'xtensa_replay',
>> ]
>>
>> +# Tests that require a specific runner.
>> +gdb = find_program('gdb-multiarch', required: false)
>> +if gdb.found()
>> + gdb_runner_script = meson.project_source_root() + '/tests/guest-debug/run-test.py'
>> + gdb_runner = [gdb_runner_script, '--gdb', gdb, '--test']
>> +
>> + # A test with a runner is a tuple (name, runner, protocol).
>> + # The tests must be elements of an array named like:
>> + #
>> + # test_<arch>_<mode=[system|linuxuser|bsduser]>_<speed=[quick|thorough]>_with_runner = [
>> + # ['test0', gdb_runner, 'exitcode'],
>> + # ...
>> + # ]
>> +else
>> + message('GDB multiarch not found, skipping functional tests that rely on it.')
>> +endif
>> +
>
> We already have a --gdb option in configure which sets GDB= for
> check-tcg - we should use the same configuration for these tests. You
> may need to convert the configure probe to a meson-option.
True. I'll sort it out in v2. Afaics it will solve the issue Thomas found on
Fedora. As Daniel says gdb in Fedora already has all the arch built-in, the
detection in configure will work. Thanks.
Cheers,
Gustavo
>> precache_all = []
>> foreach speed : ['quick', 'thorough']
>> foreach dir : target_dirs
>> @@ -372,9 +389,11 @@ foreach speed : ['quick', 'thorough']
>> suites = ['func-quick', 'func-' + target_base]
>> target_tests = get_variable('tests_' + target_base + '_' + sysmode + '_quick', []) \
>> + get_variable('tests_generic_' + sysmode)
>> + target_tests_r = get_variable('tests_' + target_base + '_' + sysmode + '_quick_with_runner', [])
>> else
>> suites = ['func-' + speed, 'func-' + target_base + '-' + speed, speed]
>> target_tests = get_variable('tests_' + target_base + '_' + sysmode + '_' + speed, [])
>> + target_tests_r = get_variable('tests_' + target_base + '_' + sysmode + '_' + speed + '_with_runner', [])
>> endif
>>
>> test_deps = [roms, keymap_targets]
>> @@ -423,6 +442,49 @@ foreach speed : ['quick', 'thorough']
>> priority: test_timeouts.get(test, 90),
>> suite: suites)
>> endforeach
>> +
>> + # Prepare tests that require a specific runner.
>> + foreach test : target_tests_r
>> + testname = '@0@-@1@'.format(target_base, test[0])
>> + testfile = 'test_' + test[0] + '.py'
>> + testpath = meson.current_source_dir() / testfile
>> + teststamp = testname + '.tstamp'
>> + testrunner = test[1]
>> + testproto = test[2]
>> +
>> + test_precache_env = environment()
>> + test_precache_env.set('QEMU_TEST_PRECACHE', meson.current_build_dir() / teststamp)
>> + # python_site_packages, i.e., site packages from Python in pyvenv, is
>> + # added to PYTHONPATH because some runners can run a program that has its
>> + # own Python hooks that, by its turn, will search for modules based on
>> + # PYTHONPATH independently of the Python used by the runner, like, for
>> + # example, GDB using libpython.
>> + test_precache_env.set('PYTHONPATH', meson.project_source_root() / 'python' +
>> + ':' + meson.current_source_dir() +
>> + ':' + python_site_packages)
>> + precache = custom_target('func-precache-' + testname,
>> + output: teststamp,
>> + command: [testrunner, testpath],
>> + depend_files: files(testpath),
>> + build_by_default: false,
>> + env: test_precache_env)
>> + precache_all += precache
>> +
>> + # See comment above about python_site_packages in test_precache_env.
>> + # Don't append to test_env since it will affect previous uses of it.
>> + test_r_env = test_env
>> + test_r_env.append('PYTHONPATH', python_site_packages)
>> +
>> + test('func-' + testname,
>> + python,
>> + depends: [test_deps, test_emulator, emulator_modules, plugin_modules],
>> + env: test_r_env,
>> + args: [testrunner, testpath],
>> + protocol: testproto,
>> + timeout: test_timeouts.get(test[0], 90),
>> + priority: test_timeouts.get(test[0], 90),
>> + suite: suites)
>> + endforeach
>> endforeach
>> endforeach
>
next prev parent reply other threads:[~2025-08-26 15:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 14:39 [PATCH 0/4] tests/functional: Adapt reverse_debugging to run w/o Avocado Gustavo Romero
2025-08-19 14:39 ` [PATCH 1/4] tests/guest-debug: Make QEMU optional in run-test.py Gustavo Romero
2025-08-25 17:01 ` Alex Bennée
2025-08-25 17:26 ` Gustavo Romero
2025-08-25 17:30 ` Gustavo Romero
2025-08-25 21:24 ` Alex Bennée
2025-08-19 14:39 ` [PATCH 2/4] tests/functional: Support tests that require a runner Gustavo Romero
2025-08-25 16:50 ` Alex Bennée
2025-08-26 15:20 ` Gustavo Romero [this message]
2025-08-19 14:39 ` [PATCH 3/4] tests/functional: Mark main in QemuBaseTest class as a static method Gustavo Romero
2025-08-19 14:54 ` Daniel P. Berrangé
2025-08-19 14:39 ` [PATCH 4/4] tests/functional: Adapt reverse_debugging to run w/o Avocado Gustavo Romero
2025-08-25 10:34 ` Thomas Huth
2025-08-25 14:05 ` Gustavo Romero
2025-08-27 1:23 ` Gustavo Romero
2025-08-25 10:29 ` [PATCH 0/4] " Thomas Huth
2025-08-25 11:00 ` Manos Pitsidianakis
2025-08-25 14:56 ` Gustavo Romero
2025-08-25 14:04 ` Gustavo Romero
2025-08-26 7:51 ` Thomas Huth
2025-08-26 8:26 ` Alex Bennée
2025-08-26 8:45 ` Manos Pitsidianakis
2025-08-26 14:10 ` Daniel P. Berrangé
2025-08-26 15:22 ` Daniel P. Berrangé
2025-08-26 15:31 ` Gustavo Romero
2025-08-26 8:06 ` Thomas Huth
2025-08-26 15:02 ` Gustavo Romero
2025-08-26 13:58 ` Daniel P. Berrangé
2025-08-27 12:04 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff89f821-e0aa-4a4e-9ac9-f50a6ee062af@linaro.org \
--to=gustavo.romero@linaro.org \
--cc=1844144@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).