From: builder@sourceware.org
To: elfutils-devel@sourceware.org
Subject: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Mon, 28 Nov 2022 13:30:33 +0000 [thread overview]
Message-ID: <20221128133033.8D4283858414@sourceware.org> (raw)
A new failure has been detected on builder elfutils-debian-armhf while building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#builders/6/builds/105
Build state: failed test (failure)
Revision: 98bdf533c4990728f0db653ab4e98a503d7654ce
Worker: debian-armhf
Build Reason: (unknown)
Blamelist: Martin Liska <mliska@suse.cz>
Steps:
- 0: worker_preparation ( success )
- 1: set package name ( success )
- 2: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/2/logs/stdio
- 3: autoreconf ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/3/logs/stdio
- 4: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/4/logs/stdio
- 5: get version ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/5/logs/stdio
- property changes: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/5/logs/property_changes
- 6: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/6/logs/stdio
- warnings (3): https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/6/logs/warnings__3_
- 7: make check ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/7/logs/stdio
- test-suite.log: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/7/logs/test-suite_log
- 8: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/8/logs/stdio
- 9: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/9/logs/stdio
- 10: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/10/logs/stdio
- 11: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/11/logs/stdio
- 12: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/12/logs/stdio
- 13: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/13/logs/stdio
- 14: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/14/logs/stdio
- 15: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/15/logs/stdio
- 16: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/16/logs/stdio
- 17: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/17/logs/stdio
- 18: make distclean ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/105/steps/18/logs/stdio
next reply other threads:[~2022-11-28 13:30 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:30 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02 1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-17 9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02 ` Frank Ch. Eigler
2022-10-17 14:09 ` Frank Ch. Eigler
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-07-31 23:54 builder
2022-08-01 0:09 ` Mark Wielaard
2022-08-01 9:13 ` Mark Wielaard
2022-05-28 9:15 builder
2022-05-28 9:35 ` Mark Wielaard
2022-05-28 9:43 ` Mark Wielaard
2022-06-02 15:44 ` Mark Wielaard
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28 2:34 ` Frank Ch. Eigler
2022-05-28 9:04 ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard
2022-04-23 13:19 builder
2022-04-23 1:19 builder
2022-04-23 1:31 ` Mark Wielaard
2022-04-19 9:05 builder
2022-04-19 9:28 ` 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=20221128133033.8D4283858414@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).