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: Sun, 16 Oct 2022 17:11:47 +0000 [thread overview] Message-ID: <20221016171147.253113858C83@sourceware.org> (raw) A retry build has been detected on builder gdb-debian-armhf while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/72/builds/1027 Build state: retry lost connection compile (retry) Revision: 517a63c2c48e5aaabe57de079e2d7f0bea09429b Worker: debian-armhf Build Reason: (unknown) Blamelist: Simon Marchi <simon.marchi@efficios.com>, Simon Marchi <simon.marchi@polymtl.ca> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1027/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1027/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1027/steps/3/logs/stdio - 4: make ( retry ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1027/steps/4/logs/stdio - cancelled: https://builder.sourceware.org/buildbot/#builders/72/builds/1027/steps/4/logs/cancelled A new failure has been detected on builder gdb-debian-armhf while building binutils-gdb. Full details are available at: https://builder.sourceware.org/buildbot/#builders/72/builds/1028 Build state: failed compile (failure) Revision: 517a63c2c48e5aaabe57de079e2d7f0bea09429b Worker: debian-armhf Build Reason: (unknown) Blamelist: Simon Marchi <simon.marchi@efficios.com>, Simon Marchi <simon.marchi@polymtl.ca> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1028/steps/1/logs/stdio - 2: rm -rf gdb-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1028/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1028/steps/3/logs/stdio - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/1028/steps/4/logs/stdio - warnings (20): https://builder.sourceware.org/buildbot/#builders/72/builds/1028/steps/4/logs/warnings__20_
next reply other threads:[~2022-10-16 17:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-16 17:11 builder [this message] 2022-10-16 17:29 builder 2022-12-20 11: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=20221016171147.253113858C83@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).