public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gdb-testers@sourceware.org Subject: ☝ Buildbot (Sourceware): binutils-gdb - retry lost connection compile (retry) (master) Date: Fri, 19 Apr 2024 03:31:52 +0000 [thread overview] Message-ID: <20240419033152.4733E3864830@sourceware.org> (raw) A retry build has been detected on builder gdb-ubuntu-riscv while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/294/builds/183 Build state: retry lost connection compile (retry) Revision: 2304772225e51cb939d3766cde47d7651d15176e Worker: starfive-4 Build Reason: (unknown) Blamelist: Alan Modra <amodra@gmail.com>, GDB Administrator <gdbadmin@sourceware.org> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/3/logs/config_log - 4: make ( retry ) Logs: - stdio: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/4/logs/stdio - cancelled: https://builder.sourceware.org/buildbot/#/builders/294/builds/183/steps/4/logs/cancelled
next reply other threads:[~2024-04-19 3:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-19 3:31 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-19 3:30 builder 2024-01-10 15:51 builder 2024-01-09 15:32 builder 2024-01-09 15:29 builder 2024-01-09 13:17 builder 2024-01-09 6:20 builder 2023-12-05 6:57 builder 2023-11-21 14:28 builder 2023-10-20 2:02 builder 2023-09-29 15:40 builder 2023-03-23 14:54 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=20240419033152.4733E3864830@sourceware.org \ --to=builder@sourceware.org \ --cc=gdb-testers@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: 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).