unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66059-done@debbugs.gnu.org
Subject: bug#66059: [cuirass] [feature] Mention which builder machine was used
Date: Fri, 22 Sep 2023 10:21:43 +0200	[thread overview]
Message-ID: <87cyyabotk.fsf@gnu.org> (raw)
In-Reply-To: <878r948v9m.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 17 Sep 2023 15:17:09 -0400")

Hi Maxim,

Maxim Cournoyer <maxim.cournoyer@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’.




      reply	other threads:[~2023-09-22  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 19:17 bug#66059: [cuirass] [feature] Mention which builder machine was used Maxim Cournoyer
2023-09-22  8:21 ` Ludovic Courtès [this message]

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=87cyyabotk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66059-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).