From: builder@sourceware.org
To: debugedit@sourceware.org
Subject: ☝ Buildbot (Sourceware): debugedit - worker not available (main)
Date: Tue, 20 Aug 2024 20:26:21 +0000 [thread overview]
Message-ID: <20240820202622.027D63858D34@sourceware.org> (raw)
A retry build has been detected on builder debugedit-opensuseleap-x86_64 while building debugedit.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/95/builds/28
Build state: worker not available
Revision: (unknown)
Worker: bbo1-2
Build Reason: (unknown)
Blamelist: Keith Seitz <keiths@redhat.com>
Steps:
- 0: worker_preparation ( exception )
A retry build has been detected on builder debugedit-opensuseleap-x86_64 while building debugedit.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/95/builds/29
Build state: worker not available
Revision: (unknown)
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Keith Seitz <keiths@redhat.com>
Steps:
- 0: worker_preparation ( exception )
A retry build has been detected on builder debugedit-opensuseleap-x86_64 while building debugedit.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/95/builds/30
Build state: worker not available
Revision: (unknown)
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Keith Seitz <keiths@redhat.com>
Steps:
- 0: worker_preparation ( exception )
A retry build has been detected on builder debugedit-opensuseleap-x86_64 while building debugedit.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/95/builds/31
Build state: worker not available
Revision: (unknown)
Worker: bbo1-2
Build Reason: (unknown)
Blamelist: Keith Seitz <keiths@redhat.com>
Steps:
- 0: worker_preparation ( exception )
A retry build has been detected on builder debugedit-opensuseleap-x86_64 while building debugedit.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/95/builds/32
Build state: worker not available
Revision: (unknown)
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Keith Seitz <keiths@redhat.com>
Steps:
- 0: worker_preparation ( exception )
reply other threads:[~2024-08-20 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240820202622.027D63858D34@sourceware.org \
--to=builder@sourceware.org \
--cc=debugedit@sourceware.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.
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).