From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 32954@debbugs.gnu.org
Subject: bug#32954: Cuirass: logs of failing tests are unavailable
Date: Mon, 08 Oct 2018 22:30:08 +0200 [thread overview]
Message-ID: <87h8hww59r.fsf@gnu.org> (raw)
In-Reply-To: <87efd0k0p7.fsf@lassieur.org> ("Clément Lassieur"'s message of "Mon, 08 Oct 2018 15:49:40 +0200")
Hello,
Clément Lassieur <clement@lassieur.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello Clément,
>>
>> Clément Lassieur <clement@lassieur.org> skribis:
>>
>>> The logs of failing tests are unavailable.
>>>
>>> (Which makes it impossible to understand why a huge lot of tests are
>>> failing.)
>>
>> You mean the ‘test.basic.x86_64-linux’ etc. jobs, right?
>>
>> I believe the reason build logs are missing is that those jobs are
>> actually in “dependency-failed” state, and not just “failed”. IOW
>> there’s simply no build log available.
>
> I understand, but I would have expected to see a log like the one in
> https://bugs.gnu.org/32966. Wouldn't it be helpful? Also, is it
> difficult to implement?
Log files in /var/log/guix/drvs are per-derivation. If a derivation has
not been built at all, it doesn’t have a log file.
What we would need is a link to the failed dependency(ies).
Thanks,
Ludo’.
prev parent reply other threads:[~2018-10-08 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 13:48 bug#32954: Cuirass: logs of failing tests are unavailable Clément Lassieur
2018-10-08 13:21 ` Ludovic Courtès
2018-10-08 13:49 ` Clément Lassieur
2018-10-08 20:30 ` 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=87h8hww59r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32954@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).