unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 38232@debbugs.gnu.org
Subject: bug#38232: Cuirass: Some builds fail although their log file ends with 'build-succeeded'
Date: Mon, 18 Nov 2019 21:22:20 +0100	[thread overview]
Message-ID: <87blt9gcjn.fsf@gnu.org> (raw)
In-Reply-To: <877e3xjevh.fsf@lassieur.org> ("Clément Lassieur"'s message of "Mon, 18 Nov 2019 18:03:46 +0100")

Hello,

Clément Lassieur <clement@lassieur.org> skribis:

>> Perhaps the build failed (transient failure or something) but was
>> eventually restarted either as a dependency of some other build or
>> manually on berlin.  In that case Cuirass may be unaware that the build
>> eventually succeeded, hence the discrepancy.
>
> Thank you for the explanation.  Would it make sense to copy the log file
> to some other place when the build is done?  The web interface would
> fetch it there, and we would be sure it matches the associated Cuirass
> build.

Build logs are kept by guix-daemon under /var/log/guix/drvs.  They are
indexed by derivation, meaning that there can be only one log per
derivation.

This is a limitation in cases where builds are retried.  Initially
Mathieu Lirzin thought about keeping logs elsewhere so we could
distinguish between several attempts to build a derivation.  However,
that’s kind of redundant with what the daemon does, and not frequently
useful.

Now, it is indeed useful in some cases, so we could do something like
you describe.

Thanks,
Ludo’.

      reply	other threads:[~2019-11-18 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 18:26 bug#38232: Cuirass: Some builds fail although their log file ends with 'build-succeeded' Clément Lassieur
2019-11-17  8:27 ` Mathieu Othacehe
2019-11-17 10:56   ` Mathieu Othacehe
2021-03-25 13:06     ` Mathieu Othacehe
2019-11-17 21:24 ` Ludovic Courtès
2019-11-18 17:03   ` Clément Lassieur
2019-11-18 20:22     ` 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=87blt9gcjn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38232@debbugs.gnu.org \
    --cc=clement@lassieur.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).