From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) test (failure) (master)
Date: Mon, 05 Sep 2022 17:45:57 +0000 [thread overview]
Message-ID: <20220905174557.D0DED385AC1B@sourceware.org> (raw)
A new failure has been detected on builder elfutils-debian-testing-x86_64 while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/145/builds/28
Build state: failed test (failure) test (failure)
Revision: a176b6e30aa8983c95b81f18c34a2b5c6a0c907b
Worker: bb1-2
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>
Steps:
- 0: worker_preparation ( success )
- 1: set package name ( success )
- 2: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/4/logs/stdio
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/5/logs/property_changes
- 6: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/6/logs/stdio
- warnings (3): https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/6/logs/warnings__3_
- 7: make check ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/7/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/7/logs/test-suite_log
- 8: make distcheck ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/8/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/8/logs/test-suite_log
- warnings (2): https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/8/logs/warnings__2_
- 9: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/9/logs/stdio
- 10: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/10/logs/stdio
- 11: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/11/logs/stdio
- 12: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/12/logs/stdio
- 13: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/13/logs/stdio
- 14: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/14/logs/stdio
- 15: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/15/logs/stdio
- 16: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/16/logs/stdio
- 17: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/17/logs/stdio
- 18: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/18/logs/stdio
- 19: make distclean ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/145/builds/28/steps/19/logs/stdio
reply other threads:[~2022-09-05 17:45 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=20220905174557.D0DED385AC1B@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).