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 - retry lost connection compile (retry) (master) Date: Thu, 18 Jan 2024 08:51:09 +0000 [thread overview] Message-ID: <20240118085109.35EF33858C42@sourceware.org> (raw) A retry build has been detected on builder gcc-fedora-mingw while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172 Build state: retry lost connection compile (retry) Revision: 1203fc2e6a40c65896763554f62cacfb4bd6a836 Worker: bbo1-1 Build Reason: (unknown) Blamelist: Jakub Jelinek <jakub@redhat.com>, Juzhe-Zhong <juzhe.zhong@rivai.ai>, Richard Biener <rguenther@suse.de>, chenxiaolong <chenxiaolong@loongson.cn> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/3/logs/config_log - 4: make ( retry ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/4/logs/stdio - cancelled: https://builder.sourceware.org/buildbot/#/builders/262/builds/4172/steps/4/logs/cancelled
next reply other threads:[~2024-01-18 8:51 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 8:51 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-24 3:15 builder 2024-03-03 22:14 builder 2024-03-03 2:56 builder 2024-02-02 14:45 builder 2024-02-01 6:44 builder 2024-01-18 9:20 builder 2024-01-10 11:27 builder 2023-11-17 13:40 builder 2023-11-15 8:05 builder 2023-11-09 8:45 builder 2023-11-02 3:45 builder 2023-09-29 22:43 builder 2023-09-29 15:17 builder 2023-09-18 9:31 builder 2023-09-09 4:58 builder 2023-09-07 10:48 builder 2023-09-07 10:05 builder 2023-08-24 10:04 builder 2023-06-29 9:29 builder 2023-06-28 7:56 builder 2023-04-20 2:02 builder 2023-04-04 13:57 builder 2023-03-09 9:05 builder 2023-03-08 5:09 builder 2023-02-23 9:53 builder 2023-01-31 14:54 builder 2023-01-18 19:13 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=20240118085109.35EF33858C42@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).