From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org, "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: core-updates-frozen: Planning for the last world rebuild
Date: Thu, 30 Sep 2021 12:29:19 -0300 [thread overview]
Message-ID: <5775742.z2ortzGu8z@popigai> (raw)
In-Reply-To: <871r56wi2v.fsf@gnu.org>
Hello Mathieu,
Em quinta-feira, 30 de setembro de 2021, às 06:03:52 -03, Mathieu Othacehe
escreveu:
> Hey Thiago,
>
> > I was waiting for this world rebuild to happen to see the results in
> > Cuirass now that powerpc64le-linux builds are only done on guixp9, but
> > in hindsight it would have been better if I requested that those
> > builds were restarted instead. Restarting this build should remove the
> > main roadblock though:
> >
> > https://ci.guix.gnu.org/build/703194/details
>
> Now restarted!
Thank you! Unfortunately that build is now affected by an issue that I only
noticed yesterday: powerpc64le-linux builds for core-updates-frozen get
permanently stuck in the ‘Scheduled’ state, even though guixp9 is
completely idle (as it is right now).
For example, this evaluation from Sep 17 has thousands of scheduled
evaluations:
https://ci.guix.gnu.org/eval/19271?status=pending
This is also happening with at least one other platform as well. This
evaluation from Sep 25 has a lot of scheduled evaluations for i586-gnu (as
well as powerpc64le-linux):
https://ci.guix.gnu.org/eval/23187?status=pending
> > When that build is restarted and succeeds, does Cuirass also restart
> > the
> > builds that failed because they depended on it, or do we need to
> > explicitly restart those as well?
>
> Yes, on successful build completion Cuirass looks if some builds that
> were marked as "failed-dependency" (failing because some of the
> dependencies are also failing) can be resumed.
That is awesome!
> That being said, Cuirass is not performing nicely these days because of:
> this issue https://issues.guix.gnu.org/48468.
Ah, ok. Thank you for the heads up.
--
Thanks,
Thiago
next prev parent reply other threads:[~2021-09-30 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 11:57 core-updates-frozen: Planning for the last world rebuild Ludovic Courtès
2021-09-28 12:20 ` Mathieu Othacehe
2021-09-29 19:54 ` Mathieu Othacehe
2021-09-30 17:44 ` Ricardo Wurmus
2021-10-01 7:16 ` Mathieu Othacehe
2021-10-01 20:13 ` Ricardo Wurmus
2021-10-05 19:24 ` Mathieu Othacehe
2021-09-30 1:32 ` Thiago Jung Bauermann
2021-09-30 9:03 ` Mathieu Othacehe
2021-09-30 15:29 ` Thiago Jung Bauermann [this message]
2021-10-01 6:21 ` Mathieu Othacehe
2021-10-01 21:51 ` Thiago Jung Bauermann
2021-09-30 8:55 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2021-09-28 19:18 John Kehayias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5775742.z2ortzGu8z@popigai \
--to=bauermann@kolabnow.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).