public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gdb-testers@sourceware.org Subject: ☝ Buildbot (GNU Toolchain): binutils-gdb - retry lost connection compile (retry) (master) Date: Tue, 20 Dec 2022 11:11:44 +0000 [thread overview] Message-ID: <20221220111144.0E9833858425@sourceware.org> (raw) A retry build has been detected on builder gdb-fedora-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/74/builds/2135 Build state: retry lost connection compile (retry) Revision: 106791196f98a0f21babf4dd46a731b5d1747d3b Worker: bb1-2 Build Reason: (unknown) Blamelist: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/2135/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/2135/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/2135/steps/3/logs/stdio - 4: make ( retry ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/74/builds/2135/steps/4/logs/stdio - cancelled: https://builder.sourceware.org/buildbot/#builders/74/builds/2135/steps/4/logs/cancelled A retry build has been detected on builder gdb-debian-i386 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/105/builds/1627 Build state: worker not pinged Revision: (unknown) Worker: debian-i386 Build Reason: (unknown) Blamelist: Alan Modra <amodra@gmail.com>, Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Steps: - 0: worker_preparation ( exception ) Logs: - err.text: https://builder.sourceware.org/buildbot/#builders/105/builds/1627/steps/0/logs/err_text - err.html: https://builder.sourceware.org/buildbot/#builders/105/builds/1627/steps/0/logs/err_html A retry build has been detected on builder gdb-debian-testing-x86_64 while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/148/builds/1509 Build state: retry lost connection compile (retry) Revision: 106791196f98a0f21babf4dd46a731b5d1747d3b Worker: bb3 Build Reason: (unknown) Blamelist: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/1509/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/1509/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/1509/steps/3/logs/stdio - 4: make ( retry ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/1509/steps/4/logs/stdio - cancelled: https://builder.sourceware.org/buildbot/#builders/148/builds/1509/steps/4/logs/cancelled
next reply other threads:[~2022-12-20 11:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-20 11:11 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-10-16 17:29 builder 2022-10-16 17:11 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=20221220111144.0E9833858425@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).