public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gcc-testresults@gcc.gnu.org
Subject: ☝ Buildbot (Sourceware): gcc - worker not available (master)
Date: Wed, 08 Mar 2023 05:19:12 +0000	[thread overview]
Message-ID: <20230308051912.3C96D3858410@sourceware.org> (raw)

A retry build has been detected on builder gcc-fedora-x86_64 while building gcc.

Full details are available at:
    https://builder.sourceware.org/buildbot/#builders/159/builds/3315

Build state: worker not available
Revision: (unknown)
Worker: bbo1-2
Build Reason: (unknown)
Blamelist: Jeff Law <jlaw@ventanamicro>

Steps:

- 0: worker_preparation ( exception )
    Logs:
        - err.text: https://builder.sourceware.org/buildbot/#builders/159/builds/3315/steps/0/logs/err_text
        - err.html: https://builder.sourceware.org/buildbot/#builders/159/builds/3315/steps/0/logs/err_html


             reply	other threads:[~2023-03-08  5:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  5:19 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-11 10:32 builder
2024-04-03 23:00 builder
2024-03-21 18:29 builder
2024-03-04  1:58 builder
2024-02-17  0:09 builder
2024-02-15 13:33 builder
2024-01-30 17:32 builder
2024-01-26 22:23 builder
2024-01-21 22:49 builder
2024-01-21 21:59 builder
2024-01-21 21:37 builder
2024-01-21 21:02 builder
2024-01-21 19:04 builder
2024-01-21 14:21 builder
2024-01-20 11:59 builder
2024-01-18 16:54 builder
2024-01-18 15:15 builder
2024-01-18 14:10 builder
2024-01-11 19:03 builder
2023-11-23  3:18 builder
2023-11-23  2:42 builder
2023-11-23  0:19 builder
2023-11-22 18:55 builder
2023-11-05 14:33 builder
2023-11-05 11:13 builder
2023-11-05  5:02 builder
2023-09-05 18:31 builder
2023-07-31 15:21 builder
2023-07-17  3:58 builder
2023-07-10 13:17 builder
2023-06-01 15:03 builder
2023-02-01 19:38 builder
2023-02-01 17:51 builder
2023-02-01 15:23 builder
2023-02-01 14:23 builder

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=20230308051912.3C96D3858410@sourceware.org \
    --to=builder@sourceware.org \
    --cc=gcc-testresults@gcc.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. 
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).