emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#46402: closed (Cuirass rebuilds the same packae multiple times)


From: GNU bug Tracking System
Subject: bug#46402: closed (Cuirass rebuilds the same packae multiple times)
Date: Fri, 28 May 2021 12:52:02 +0000

Your message dated Fri, 28 May 2021 14:51:48 +0200
with message-id <87wnrjf2cb.fsf@gnu.org>
and subject line Re: bug#46402: Cuirass rebuilds the same packae multiple times
has caused the debbugs.gnu.org bug report #46402,
regarding Cuirass rebuilds the same packae multiple times
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
46402: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46402
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Cuirass rebuilds the same packae multiple times Date: Tue, 9 Feb 2021 14:19:15 +0100
Hi!

I've updated php yesterday and I noticed that cuirass is now busy
building dependents on aarch64. Looking at the log of some of them, it
seems that the workers are independently building the same php
derivation, and not the dependents, at the same time. This is extremely
wasteful as php is very long to build (and might even eventually fail).

here is an example: https://ci.guix.gnu.org/build/287478/details and
https://ci.guix.gnu.org/build/287476/details are being built at the
same time, and the logs currently show they are both running the test
phase of the php package.

Shouldn't cuirass first schedule builds for dependencies before it
builds dependents?



--- End Message ---
--- Begin Message --- Subject: Re: bug#46402: Cuirass rebuilds the same packae multiple times Date: Fri, 28 May 2021 14:51:48 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hello,

> Shouldn't cuirass first schedule builds for dependencies before it
> builds dependents?

Yes fixed with
https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=d1a95e8b33b454a45bda506a22a8b9d9d2c8b16e.

Thanks,

Mathieu


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]