Replies: 1 comment
|
https://mesonbuild.com/Reference-manual_functions.html#add_test_setup add_test_setup('default', is_default: true, exclude_suites: ['legacy'])And add test-old-large-exec to the "legacy" suite. This allows you to use |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I've got a suite of tests that run under meson which I've recently made changes to so that they can be run in parallel. Think: splitting a single large test executable into multiple, independent executables that meson can run in parallel.
However, I need to make sure that the old, large single executable continues to function for the sake of compatibility with other tools.
That having been said, I don't want the old, large single executable to run as part of the default
meson testinvocation. I only want it to run when it's specifically called by name, i.e.meson test test-old-large-exec.Is there some undocumented exclusion parameter, or negation that I can apply to the
testdefinition in mymeson.buildfile that I can use to prevent this suite from being run, while keeping it defined and easy to run if a user wants to.Thanks,
M
All reactions