From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☝ Buildbot (GNU Toolchain): elfutils - retry lost connection test (retry) (master)
Date: Wed, 11 Jan 2023 15:41:33 +0000 [thread overview]
Message-ID: <20230111154133.0A7F43858D38@sourceware.org> (raw)
A retry build has been detected on builder elfutils-debian-ppc64 while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/63/builds/126
Build state: retry lost connection test (retry)
Revision: 6560fb26a62ef135a804357ef4f15a47de3e49b3
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Mark Wielaard <mark@klomp.org>
Steps:
- 0: worker_preparation ( success )
- 1: set package name ( success )
- 2: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/4/logs/stdio
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/5/logs/property_changes
- 6: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/6/logs/stdio
- warnings (3): https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/6/logs/warnings__3_
- 7: make check ( retry )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/7/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/7/logs/test-suite_log
- cancelled: https://builder.sourceware.org/buildbot/#builders/63/builds/126/steps/7/logs/cancelled
reply other threads:[~2023-01-11 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230111154133.0A7F43858D38@sourceware.org \
--to=builder@sourceware.org \
--cc=elfutils-devel@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: link
Be 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).