On Sun, Apr 6, 2025 at 1:34 AM Sam James <s...@gentoo.org> wrote: > > Newer versions of meson [0] don't build all test targets upfront (which > makes this more noticeable, still was a thing before w/ custom handling) > so, in the common case, test binaries are built by the `meson test` call. > > That means their compile/link lines aren't emitted (even with `meson test > --verbose`) > and they're also built without respecting $(makeopts_jobs) as `meson test > --num-processes` only affects test execution parallelism. > > Preempt that by calling `eninja meson-test-prereq` first which solves both > problems. We can safely do this unconditionally as this target was added > in meson-0.63.0 and we depend on >=meson-1.2.3 in the eclass.
I think this change will break sys-apps/systemd-utils, which builds only a subset of the available test binaries. It's probably fine in most cases, I just wanted to point it out.
