GNU bug report logs - #62995
Cuirass evaluation failures not reported as such

Previous Next

Package: guix;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Fri, 21 Apr 2023 14:44:02 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 62995 in the body.
You can then email your comments to 62995 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#62995; Package guix. (Fri, 21 Apr 2023 14:44:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ludovic Courtès <ludo <at> gnu.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Fri, 21 Apr 2023 14:44:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: Cuirass evaluation failures not reported as such
Date: Fri, 21 Apr 2023 16:42:56 +0200
I noticed that evaluation failures are not (not always?) being reported
with a ❎ as it used to be.  For example:

  https://ci.guix.gnu.org/eval/418466

It is marked as successful but it has zero build jobs:

  https://ci.guix.gnu.org/eval/418466/dashboard

The evaluation log on berlin shows a clear failure though:

--8<---------------cut here---------------start------------->8---
ludo <at> berlin ~$ zcat /var/log/cuirass/evaluations/418466.gz
Computing Guix derivation for 'x86_64-linux'...  
In thread:
socket:21:111: Unknown # object: "#<"
--8<---------------cut here---------------end--------------->8---

Ludo’.




Reply sent to Ludovic Courtès <ludo <at> gnu.org>:
You have taken responsibility. (Fri, 19 May 2023 14:40:02 GMT) Full text and rfc822 format available.

Notification sent to Ludovic Courtès <ludo <at> gnu.org>:
bug acknowledged by developer. (Fri, 19 May 2023 14:40:02 GMT) Full text and rfc822 format available.

Message #10 received at 62995-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: 62995-done <at> debbugs.gnu.org
Subject: Re: bug#62995: Cuirass evaluation failures not reported as such
Date: Fri, 19 May 2023 16:39:10 +0200
Ludovic Courtès <ludo <at> gnu.org> skribis:

> I noticed that evaluation failures are not (not always?) being reported
> with a ❎ as it used to be.  For example:
>
>   https://ci.guix.gnu.org/eval/418466
>
> It is marked as successful but it has zero build jobs:
>
>   https://ci.guix.gnu.org/eval/418466/dashboard
>
> The evaluation log on berlin shows a clear failure though:
>
> ludo <at> berlin ~$ zcat /var/log/cuirass/evaluations/418466.gz
> Computing Guix derivation for 'x86_64-linux'...  
> In thread:
> socket:21:111: Unknown # object: "#<"

I believe this was fixed by Cuirass commit
899391215045513ddd708b12edade8de71e29b9e.

Ludo’.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 17 Jun 2023 11:24:12 GMT) Full text and rfc822 format available.

This bug report was last modified 307 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.