unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: 38232@debbugs.gnu.org
Subject: bug#38232: Cuirass: Some builds fail although their log file ends with 'build-succeeded'
Date: Sun, 17 Nov 2019 11:56:41 +0100	[thread overview]
Message-ID: <8736emvkie.fsf@gmail.com> (raw)
In-Reply-To: <874kz2vrem.fsf@gmail.com>


> It seems to be also an issue for evaluations that look successful but
> are reported as failed, see here:

Looking at those evaluation logs, I think there is yet another issue. On
core-updates:

* Evaluation 8747 fails because it cannot build curl
(https://ci.guix.gnu.org/eval/8748/log/raw).

* Next evaluation 8762, considers curl build as previously failed:
--8<---------------cut here---------------start------------->8---
Computing Guix derivation for 'x86_64-linux'...  builder for `/gnu/store/1510sg9h2ivq4841gqm9dhmq5l50a52b-curl-7.66.0' failed previously (cached)
@ build-failed /gnu/store/pqfnxfk5xx0ngc32wlq87vhchh80mnkw-curl-7.66.0.drv - cached--8<---------------cut here---------------end--------------->8---
and fails immediately.

The curl build problem (at 8747 evaluation) seems related to some failed
test case (1242) that I cannot reproduce locally.

Will all future evaluations re-use this cache and also fail immediately?
If yes, how can we unblock the situation?

Mathieu

  reply	other threads:[~2019-11-17 10:57 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 [this message]
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

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=8736emvkie.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=38232@debbugs.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).