GNU bug report logs - #63413
Stop and restart builds in cuirass

Previous Next

Package: guix;

Reported by: Andreas Enge <andreas <at> enge.fr>

Date: Wed, 10 May 2023 10:30:03 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #10 received at 63413-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Andreas Enge <andreas <at> enge.fr>
Cc: 63413-done <at> debbugs.gnu.org
Subject: Re: bug#63413: Stop and restart builds in cuirass
Date: Tue, 04 Jun 2024 15:59:53 +0200
Hi Andreas,

Andreas Enge <andreas <at> enge.fr> skribis:

> Stopping and starting builds in cuirass is not very comfortable.
>
> When working on core-updates, I stopped builds for some old evaluations
> on aarch64, where our build power would not be enough, assuming that many
> of the old builds were made obsolete by newer changes. (For instance,
> these could be builds in branches that were already merged to master.)
>
> However, this also stopped the builds that were not obsolete. And if the
> derivation was unchanged in a later evaluation (or a different branch),
> it would be kept as failed and not be restarted. I would argue that the
> desirable behaviour would be to try all derivations in a new evaluation,
> regardless of whether they were stopped in a previous evaluation.

(For clarity: s/stop/cancel/ above.)

I’m happy to report that this bug should be fixed in the snapshot
recently deployed on ci.guix.gnu.org.  The fix is here:

  https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=12d79854ee7685b356a72ca374f2a90b8efe5903

Lemme know if it turns out to be a broken fix!

Ludo’.




This bug report was last modified 1 year and 81 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.