[cuirass] Bogus (ancient) notifications sent

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

Debbugs page

Maxim Cournoyer wrote 1 years ago
(name . bug-guix)(address . bug-guix@gnu.org)
87zfxnmrkv.fsf@gmail.com
Hello,

Following the qt-team branch builds, I just received today:

Toggle snippet (12 lines)
From: cuirass@gnu.org (Cuirass)
Subject: Build sound-juicer.aarch64-linux on qt-team is broken.
Newsgroups: qt-team
Date: Thu, 01 Jan 1970 01:00:00 +0000 (54 years, 1 day, 6 hours ago)
Attachment: [3. text/html]...

<p>The build <b>sound-juicer.aarch64-linux</b> for specification <b>qt-team</b> is broken. You can find the detailed information about this build <a
href="https://ci.guix.gnu.org/build/2187490/details">here</a>.</p>

https://ci.guix.gnu.org/build/2187490/details

It's dated from 1970. Prior to these I got some that were 10 weeks old.
I'm not sure what these were triggered by, but that seems a bug.
Ricardo hypothesized that "maybe it finally got around to building these
queued up jobs…?", which sounds like a potential explanation.

--
Thanks,
Maxim
Maxim Cournoyer wrote 1 years ago
(address . 68223@debbugs.gnu.org)
87v88bmrfv.fsf@gmail.com
Hi,

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

Toggle quote (20 lines)
> Hello,
>
> Following the qt-team branch builds, I just received today:
>
> From: cuirass@gnu.org (Cuirass)
> Subject: Build sound-juicer.aarch64-linux on qt-team is broken.
> Newsgroups: qt-team
> Date: Thu, 01 Jan 1970 01:00:00 +0000 (54 years, 1 day, 6 hours ago)
> Attachment: [3. text/html]...
>
> <p>The build <b>sound-juicer.aarch64-linux</b> for specification <b>qt-team</b> is broken. You can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/2187490/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/2187490/details
>
> It's dated from 1970. Prior to these I got some that were 10 weeks old.
> I'm not sure what these were triggered by, but that seems a bug.
> Ricardo hypothesized that "maybe it finally got around to building these
> queued up jobs…?", which sounds like a potential explanation.

More context: these 1970 dated notifications occurred following
restarting the builds for which I had originally received 10 weeks dated
notifications. They are still marked pending as "Scheduled", so I'm not
sure why a notification was sent.

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 68223@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 68223
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
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help