From: "Clément Lassieur" <clement@lassieur.org>
To: 32583@debbugs.gnu.org
Subject: bug#32583: Cuirass: some builds are marked as failed, but they were never built
Date: Thu, 30 Aug 2018 11:44:54 +0200 [thread overview]
Message-ID: <87zhx41949.fsf@lassieur.org> (raw)
Reported by Ludovic on IRC.
Some builds are marked as failed, but they were never built. Plus,
starttime and stoptime don't make sense.
--8<---------------cut here---------------start------------->8---
<civodul> snape: i just noticed something fishy:
https://berlin.guixsd.org/build/467599 is marked as failed
[11:24]
<civodul> however,
/gnu/store/nr0w89qymmnfbcb9vw9q86p0a4v1h6w2-libsvgtiny-0.1.7.drv has
never been built
<civodul> so it's not even a dependency-failed situation
<civodul> i wonder if this could be a regression in Cuirass
<civodul> it has "starttime":0,"stoptime":1535613271 [11:25]
<civodul> which normally cannot happen (starttime shouldn't be 0 i stoptime is
not 0)
<snape> civodul: indeed it's weird [11:27]
<snape> civodul: how do you know
/gnu/store/nr0w89qymmnfbcb9vw9q86p0a4v1h6w2-libsvgtiny-0.1.7.drv has
never been built? [11:28]
<snape> well, I guess because there is no log [11:32]
<civodul> snape: yes and i ssh'd into berlin
<snape> civodul: it builds if you spawn it manually? [11:37]
<civodul> snape: i didn't let it run to completion because i wanted us to be
able to debug it [11:39]
<civodul> but most likely it does [11:40]
<civodul> (i tested with
/gnu/store/wgk46pv09m1y8b7iq5fbkhay5hs6hnmr-libcss-0.8.0.drv, which
was another build marked as failed)
--8<---------------cut here---------------end--------------->8---
Clément
next reply other threads:[~2018-08-30 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:44 Clément Lassieur [this message]
2018-09-01 23:35 ` bug#32583: Cuirass: some builds are marked as failed, but they were never built Clément Lassieur
2018-09-02 14:39 ` Ludovic Courtès
2018-11-20 9:56 ` Clément Lassieur
2018-11-20 12:44 ` 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=87zhx41949.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=32583@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).