GNU bug report logs - #66059
[cuirass] [feature] Mention which builder machine was used

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66059 in the body.
You can then email your comments to 66059 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: [cuirass] [feature] Mention which builder machine was used
Date: Sun, 17 Sep 2023 15:17:09 -0400

Hello,

When investigating a build failure, it can be useful to see the logs of
the machine that built the package (to determine whether it ran out of
memory, say), but currently the build logs or even the derivation page
on Cuirass doesn't track such information: it's not visible in the web
interface and not mentioned either in the build log.

We should add it to both places, ideally.

-- 
Thanks,
Maxim

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 66059-done <at> debbugs.gnu.org
Subject: Re: bug#66059: [cuirass] [feature] Mention which builder machine
 was used
Date: Fri, 22 Sep 2023 10:21:43 +0200

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

> When investigating a build failure, it can be useful to see the logs of
> the machine that built the package (to determine whether it ran out of
> memory, say), but currently the build logs or even the derivation page
> on Cuirass doesn't track such information: it's not visible in the web
> interface and not mentioned either in the build log.

Fixed, on the build page (we can’t really do that on the build log):

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

It was easy to do because Cuirass already keeps track of that.

However, Cuirass keeps track of the “worker” that was used, not the
machine.  A “worker” is essentially a fiber in the ‘cuirass
remote-worker’ process, with a temporary random name; when the worker
goes away, we become unable to map it back to the machine it belonged to
(I think).  Which means we’ll lose that info eventually.

(Now the whole point of normalized build environments is that knowing
which machine was used should rarely matter.)

Thanks,
Ludo’.

Previous Next

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