It is a usual workflow to fix something and retest to see if it is fixed using a particular test. When tests start to become numerous, it becomes time consuming for "meson test" to relink all of them (and in fact rebuild the whole project) where the user has already specified the tests they want to run, as well as the tests' dependencies. Teach meson to be smart and only build what is needed for the test (or suite) that were specified. Fixes: #7473 Related: #7830pull/7902/head
parent
879e9d19f5
commit
79e2c52a15
3 changed files with 61 additions and 12 deletions
@ -0,0 +1,17 @@ |
||||
## `meson test` only rebuilds test dependencies |
||||
|
||||
Until now, `meson test` rebuilt the whole project independent of the |
||||
requested tests and their dependencies. With this release, `meson test` |
||||
will only rebuild what is needed for the tests or suites that will be run. |
||||
This feature can be used, for example, to speed up bisecting regressions |
||||
using commands like the following: |
||||
|
||||
git bisect start <broken commit> <working commit> |
||||
git bisect run meson test <failing test name> |
||||
|
||||
This would find the broken commit automatically while at each step |
||||
rebuilding only those pieces of code needed to run the test. |
||||
|
||||
However, this change could cause failures if dependencies are not |
||||
specified correctly in `meson.build`. |
||||
|
Loading…
Reference in new issue