|
From: | The Man |
Subject: | [bug#73135] [PATCH] Enable parallel tests for GTK |
Date: | Fri, 4 Oct 2024 11:05:33 -0500 |
Sounds like a good idea to me.
Hi,
The Man <squishypinkelephant@gmail.com> skribis:
> In the middle of testing a set of patches that caused a large number of
> rebuilds, I noticed the gtk package was taking an obscenely long time to
> run checks. Upon inspection I found out it was not running tests as
> parallel.
> For example, https://ci.guix.gnu.org/build/5623913/details took >3000!
> seconds.
> The fix is obvious and will save time on future rebuilds.
> diff --git a/gnu/packages/gtk.scm b/gnu/packages/gtk.scm
> index 3d4766713d..f0f6a0cd9a 100644
> --- a/gnu/packages/gtk.scm
> +++ b/gnu/packages/gtk.scm
> @@ -1195,6 +1195,7 @@ (define-public gtk
> (string=? (%current-system) "aarch64-linux"))
> "--no-suite=wayland_gles2_failing"
> "--no-suite=wayland_gles_failing"))
> + #:parallel-tests? #t
I wonder why #:parallel-tests? defaults to #f in ‘meson-build-system’,
contrary to what other build systems do.
I think we should create a branch where we change it to #t, and merge it
once we’re done rebuilding all the packages and fixing any relevant
failure.
Would you like to give that a try?
Thanks,
Ludo’.
[Prev in Thread] | Current Thread | [Next in Thread] |