From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)
Date: Fri, 01 Mar 2024 00:27:29 +0000 [thread overview]
Message-ID: <20240301002729.2B55A3858409@sourceware.org> (raw)
A new failure has been detected on builder elfutils-debian-ppc64 while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/63/builds/289
Build state: failed test (failure)
Revision: d7768acc697735cc7498ddc891a1065439ba1d6f
Worker: debian-ppc64
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/63/builds/289/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/4/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/4/logs/config_log
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/5/logs/property_changes
- 6: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/6/logs/stdio
- warnings (3): https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/6/logs/warnings__3_
- 7: make check ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/7/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/7/logs/test-suite_log
- 8: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/8/logs/stdio
- 9: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/9/logs/stdio
- 10: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/10/logs/stdio
- 11: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/11/logs/stdio
- 12: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/12/logs/stdio
- 13: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/13/logs/stdio
- 14: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/14/logs/stdio
- 15: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/15/logs/stdio
- 16: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/16/logs/stdio
- 17: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/17/logs/stdio
- 18: make distclean ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/63/builds/289/steps/18/logs/stdio
next reply other threads:[~2024-03-01 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 0:27 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-27 14:44 builder
2024-03-24 17:45 builder
2024-03-24 17:54 ` Mark Wielaard
2024-03-01 2:20 builder
2023-11-16 12:09 builder
2023-11-16 17:09 ` Mark Wielaard
2023-11-13 22:38 builder
2023-11-13 23:07 ` Mark Wielaard
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=20240301002729.2B55A3858409@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).