From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 68223@debbugs.gnu.org
Subject: bug#68223: [cuirass] Bogus (ancient) notifications sent
Date: Tue, 02 Jan 2024 15:05:40 -0500 [thread overview]
Message-ID: <87v88bmrfv.fsf@gmail.com> (raw)
In-Reply-To: <87zfxnmrkv.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 02 Jan 2024 15:02:40 -0500")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> 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
prev parent reply other threads:[~2024-01-02 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <299@qt-team.nnrss>
2024-01-02 20:02 ` bug#68223: [cuirass] Bogus (ancient) notifications sent Maxim Cournoyer
2024-01-02 20:05 ` Maxim Cournoyer [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=87v88bmrfv.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=68223@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).