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 cannot substantiate (master) Date: Mon, 29 May 2023 03:09:50 +0000 [thread overview] Message-ID: <20230529030950.7494F3858D32@sourceware.org> (raw) A build exception has been detected on builder gcc-rawhide-x86_64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/158/builds/3911 Build state: worker cannot substantiate Revision: (unknown) Worker: bb1-2 Build Reason: (unknown) Blamelist: Pan Li <pan2.li@intel.com> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/158/builds/3911/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/158/builds/3911/steps/0/logs/err_html
next reply other threads:[~2023-05-29 3:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-29 3:09 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-03-25 1:17 builder 2024-01-07 16:14 builder 2023-08-13 13:57 builder 2023-05-01 7:19 builder 2023-02-12 23:02 builder 2023-02-05 18:32 builder 2023-02-01 11:43 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=20230529030950.7494F3858D32@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: linkBe 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).