[cuirass] erroneous broken report (e.g.: Build lkrg.x86_64-linux on master is broken)

  • Done
  • quality assurance status badge
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal

Debbugs page

M
M
Maxim Cournoyer wrote on 9 Dec 2023 05:22
(name . bug-guix)(address . bug-guix@gnu.org)
87ttorfr41.fsf@gmail.com
Hello,

I got this notification from Cuirass:

cuirass@gnu.org (Cuirass) writes:

Toggle quote (5 lines)
> <p>The build <b>lkrg.x86_64-linux</b> for specification <b>master</b> is broken. You can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/2602896/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/2602896/details

Looking at the page linked, the build succeeded, and there's no trace of
a recent build failing either.

--
Thanks,
Maxim
M
M
Maxim Cournoyer wrote on 12 Dec 2023 09:05
(address . 67726-done@debbugs.gnu.org)
87wmtj9wrk.fsf@gmail.com
Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

Toggle quote (16 lines)
> Hello,
>
> I got this notification from Cuirass:
>
> cuirass@gnu.org (Cuirass) writes:
>
>> <p>The build <b>lkrg.x86_64-linux</b> for specification
>> <b>master</b> is broken. You can find the detailed information about
>> this build <a
>> href="https://ci.guix.gnu.org/build/2602896/details">here</a>.</p>
>>
>> https://ci.guix.gnu.org/build/2602896/details
>
> Looking at the page linked, the build succeeded, and there's no trace of
> a recent build failing either.

I'll close this as it was an older build (I thought it was new). Gnus
retrieved older notifications as new and I got confused.

--
Thanks,
Maxim
Closed
M
M
Maxim Cournoyer wrote on 12 Dec 2023 09:05
control message for bug #67726
(address . control@debbugs.gnu.org)
87v8939wre.fsf@gmail.com
tags 67726 notabug
close 67726
quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 67726@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 67726
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch