From: builder@sourceware.org
To: binutils@sourceware.org
Subject: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)
Date: Fri, 26 Jan 2024 12:15:36 +0000 [thread overview]
Message-ID: <20240126121536.2A3743858C53@sourceware.org> (raw)
A failed build has been detected on builder binutils-debian-amd64 while building binutils-gdb.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/68/builds/3417
Build state: failed test (failure)
Revision: cd35c9fd1e67b2dd8acbda3dfa398e395b22f220
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Aaron Merey <amerey@redhat.com>, Aditya Vidyadhar Kamath <Aditya.Kamath1@ibm.com>, Alan Modra <amodra@gmail.com>, Andrew Burgess <aburgess@redhat.com>, Andrew Carlotti <andrew.carlotti@arm.com>, Cui, Lili <lili.cui@intel.com>, David Faust <david.faust@oracle.com>, Dimitar Dimitrov <dimitar@dinux.eu>, GDB Administrator <gdbadmin@sourceware.org>, Guinevere Larsen <blarsen@redhat.com>, H.J. Lu <hjl.tools@gmail.com>, Indu Bhagat <indu.bhagat@oracle.com>, Jan Beulich <jbeulich@suse.com>, Jaydeep Patil <jaydeep.patil@imgtec.com>, Lancelot SIX <lancelot.six@amd.com>, Lulu Cai <cailulu@loongson.cn>, Mark Wielaard <mark@klomp.org>, Mike Frysinger <vapier@gentoo.org>, Nick Clifton <nickc@redhat.com>, Oleg Tolmatcev <oleg.tolmatcev@gmail.com>, Paul Iannetta <piannetta@kalrayinc.com>, Saurabh Jha <saurabh.jha@arm.com>, Simon Marchi <simon.marchi@efficios.com>, Srinath Parvathaneni <srinath.parvathaneni@arm.com>, Tatsuyuki Ishi <ishitatsuyuki@gmail.com>, Thiago Jung Bauermann <thiago.bauermann@linaro.org>, Tom Tromey <tom@tromey.com>, Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>, Victor Do Nascimento <victor.donascimento@arm.com>, Vladimir Mezentsev <vladimir.mezentsev@oracle.com>, Xi Ruoyao <xry111@xry111.site>, Yang Liu <liuyang22@iscas.ac.cn>, changjiachen <changjiachen@stu.xupt.edu.cn>, mengqinggang <mengqinggang@loongson.cn>, Сергей Чернов <klen_s@mail.ru>
Steps:
- 0: worker_preparation ( success )
- 1: git checkout ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/1/logs/stdio
- 2: rm -rf binutils-build ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/2/logs/stdio
- 3: configure ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/3/logs/stdio
- config.log: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/3/logs/config_log
- 4: make ( warnings )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/4/logs/stdio
- warnings (24): https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/4/logs/warnings__24_
- 5: make check ( failure )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/stdio
- ld.sum: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/ld_sum
- ld.log: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/ld_log
- gas.sum: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/gas_sum
- gas.log: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/gas_log
- binutils.sum: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/binutils_sum
- binutils.log: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/binutils_log
- libsframe.sum: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/libsframe_sum
- libsframe.log: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/libsframe_log
- warnings (8): https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/5/logs/warnings__8_
- 6: prep ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/6/logs/stdio
- 7: build bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/7/logs/stdio
- 8: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/8/logs/stdio
- 9: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/9/logs/stdio
- 10: pass .bunsen.source.gitname ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/10/logs/stdio
- 11: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/11/logs/stdio
- 12: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/12/logs/stdio
- 13: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/13/logs/stdio
- 14: upload to bunsen ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/14/logs/stdio
- 15: clean up ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/15/logs/stdio
- 16: rm -rf binutils-build_1 ( success )
Logs:
- stdio: https://builder.sourceware.org/buildbot/#/builders/68/builds/3417/steps/16/logs/stdio
next reply other threads:[~2024-01-26 12:15 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 12:15 builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-27 1:03 builder
2024-04-20 1:18 builder
2024-04-19 22:16 builder
2024-04-19 3:32 builder
2024-04-12 6:06 builder
2024-04-03 20:45 builder
2024-02-27 5:20 builder
2024-02-27 5:03 builder
2024-01-10 12:28 builder
2023-12-29 12:19 builder
2023-12-29 4:32 builder
2023-12-29 3:57 builder
2023-12-29 3:47 builder
2023-12-13 6:51 builder
2023-10-13 0:42 builder
2023-10-16 6:48 ` Jan Beulich
2023-10-19 11:23 ` Mark Wielaard
2023-10-19 11:48 ` Jan Beulich
2023-10-10 12:24 builder
2023-10-09 17:33 builder
2023-10-08 3:07 builder
2023-10-06 0:36 builder
2023-10-05 14:02 builder
2023-10-03 0:40 builder
2023-09-29 15:32 builder
2023-09-29 0:36 builder
2023-09-27 17:01 builder
2023-09-27 9:53 builder
2023-09-26 14:41 builder
2023-09-18 8:14 builder
2023-09-18 9:04 ` Sam James
[not found] <20230914084342.10CE138555A9@sourceware.org>
2023-09-14 8:58 ` Jan Beulich
2023-09-14 18:33 ` Mark Wielaard
2023-09-14 8:43 builder
[not found] <20230818215458.6F9403858D32@sourceware.org>
2023-08-21 6:25 ` Jan Beulich
2023-08-21 8:57 ` Mark Wielaard
2023-08-18 21:54 builder
2023-08-01 14:33 builder
2023-07-17 20:31 builder
2023-07-17 16:50 builder
2023-07-17 8:19 builder
2023-07-07 10:47 builder
[not found] <20230704171241.36F7E3858C31@sourceware.org>
2023-07-05 7:19 ` Jan Beulich
2023-07-05 9:39 ` Mark Wielaard
2023-07-04 17:12 builder
2023-06-30 5:04 builder
2023-06-29 20:25 builder
2023-06-27 23:59 builder
2023-06-14 5:36 builder
2023-06-11 0:39 builder
2023-06-07 22:58 builder
2023-06-08 0:08 ` Indu Bhagat
2023-06-08 0:25 ` Mark Wielaard
[not found] <20230530134911.4B9523858D28@sourceware.org>
2023-06-06 7:02 ` mengqinggang
2023-06-05 16:17 builder
2023-06-05 4:39 builder
2023-05-30 13:49 builder
2023-05-30 5:12 builder
2023-05-19 7:36 builder
2023-05-07 0:40 builder
2023-05-03 15:12 builder
2023-05-03 6:48 builder
2023-03-07 15:07 builder
2023-03-05 0:19 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=20240126121536.2A3743858C53@sourceware.org \
--to=builder@sourceware.org \
--cc=binutils@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).