public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: builder@sourceware.org
To: gdb-testers@sourceware.org
Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) test (failure) (master)
Date: Mon, 25 Mar 2024 20:26:37 +0000 [thread overview]
Message-ID: <20240325202637.2F3683858D33@sourceware.org> (raw)
A new failure has been detected on builder gdb-debian-i386 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/105/builds/6233
Build state: failed test (failure) test (failure)
Revision: cd9b374ffe372dcaf7e4c15548cf53a301d8dcdd
Worker: debian-i386-2
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/1/logs/stdio
- 2: rm -rf gdb-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/4/logs/stdio
- warnings (22): https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/4/logs/warnings__22_
- 5: make check-gdb ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/5/logs/stdio
- gdb.sum: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/5/logs/gdb_sum
- gdb.log: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/5/logs/gdb_log
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/6/logs/stdio
- 7: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/7/logs/stdio
- 8: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/8/logs/stdio
- 9: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/9/logs/stdio
- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/10/logs/stdio
- 11: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/11/logs/stdio
- 12: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/12/logs/stdio
- 13: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/13/logs/stdio
- 14: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/14/logs/stdio
- 15: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/15/logs/stdio
- 16: make check-gdb_1 ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/16/logs/stdio
- gdb.sum: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/16/logs/gdb_sum
- gdb.log: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/16/logs/gdb_log
- 17: prep_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/17/logs/stdio
- 18: build bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/18/logs/stdio
- 19: fetch bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/19/logs/stdio
- 20: unpack bunsen.cpio.gz_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/20/logs/stdio
- 21: pass .bunsen.source.gitname_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/21/logs/stdio
- 22: pass .bunsen.source.gitdescribe_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/22/logs/stdio
- 23: pass .bunsen.source.gitbranch_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/23/logs/stdio
- 24: pass .bunsen.source.gitrepo_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/24/logs/stdio
- 25: upload to bunsen_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/25/logs/stdio
- 26: clean up_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/26/logs/stdio
- 27: make check-gdb_2 ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/27/logs/stdio
- gdb.sum: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/27/logs/gdb_sum
- gdb.log: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/27/logs/gdb_log
- 28: prep_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/28/logs/stdio
- 29: build bunsen.cpio.gz_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/29/logs/stdio
- 30: fetch bunsen.cpio.gz_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/30/logs/stdio
- 31: unpack bunsen.cpio.gz_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/31/logs/stdio
- 32: pass .bunsen.source.gitname_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/32/logs/stdio
- 33: pass .bunsen.source.gitdescribe_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/33/logs/stdio
- 34: pass .bunsen.source.gitbranch_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/34/logs/stdio
- 35: pass .bunsen.source.gitrepo_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/35/logs/stdio
- 36: upload to bunsen_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/36/logs/stdio
- 37: clean up_2 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/37/logs/stdio
- 38: rm -rf gdb-build_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/105/builds/6233/steps/38/logs/stdio
A new failure has been detected on builder gdb-ibm-power9 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/167/builds/5963
Build state: failed compile (failure)
Revision: cd9b374ffe372dcaf7e4c15548cf53a301d8dcdd
Worker: ibm_power9
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/1/logs/stdio
- 2: rm -rf gdb-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/3/logs/config_log
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/4/logs/stdio
- warnings (26): https://builder.sourceware.org/buildbot/#/builders/167/builds/5963/steps/4/logs/warnings__26_
A new failure has been detected on builder gdb-fedora-arm64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/181/builds/6022
Build state: failed compile (failure)
Revision: cd9b374ffe372dcaf7e4c15548cf53a301d8dcdd
Worker: fedora-arm64
Build Reason: (unknown)
Blamelist: Andrew Burgess <aburgess@redhat.com>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/1/logs/stdio
- 2: rm -rf gdb-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/3/logs/config_log
- 4: make ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/4/logs/stdio
- warnings (29): https://builder.sourceware.org/buildbot/#/builders/181/builds/6022/steps/4/logs/warnings__29_
next reply other threads:[~2024-03-25 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 20:26 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-22 0:34 builder
2023-10-19 19:19 builder
2023-10-05 12:37 builder
2023-10-04 19:58 builder
2023-09-19 12:47 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=20240325202637.2F3683858D33@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: 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).