From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Fri, 23 Dec 2022 14:10:18 -0800 [thread overview]
Message-ID: <f9770b56-42a4-c70c-d7dd-c772648921ef@oracle.com> (raw)
In-Reply-To: <20221223213034.62D163858425@sourceware.org>
On 12/23/22 1:30 PM, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-debian-ppc64 while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/78/builds/1218
>
> Build state: failed test (failure)
> Revision: 995bc59782363e7634fe3034aa9363528cb8b2e5
> Worker: debian-ppc64
> Build Reason: (unknown)
> Blamelist: Indu Bhagat <indu.bhagat@oracle.com>, Mike Frysinger <vapier@gentoo.org>, Simon Marchi <simon.marchi@polymtl.ca>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/1/logs/stdio
>
> - 2: rm -rf binutils-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/3/logs/stdio
>
> - 4: make ( warnings )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/4/logs/stdio
> - warnings (22): https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/4/logs/warnings__22_
>
> - 5: make check ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/stdio
> - ld.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/ld_sum
> - ld.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/ld_log
> - gas.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/gas_sum
> - gas.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/gas_log
> - binutils.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/binutils_sum
> - binutils.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/binutils_log
> - libsframe.sum: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/libsframe_sum
> - libsframe.log: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/libsframe_log
> - warnings (8): https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/5/logs/warnings__8_
>
I am looking into the failure (FAIL: encode-1: Encode buffer match).
Basically this test should not be run as is on a big endian host.
> - 6: prep ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/6/logs/stdio
>
> - 7: build bunsen.cpio.gz ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/7/logs/stdio
>
> - 8: fetch bunsen.cpio.gz ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/8/logs/stdio
>
> - 9: unpack bunsen.cpio.gz ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/9/logs/stdio
>
> - 10: pass .bunsen.source.gitname ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/10/logs/stdio
>
> - 11: pass .bunsen.source.gitdescribe ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/11/logs/stdio
>
> - 12: pass .bunsen.source.gitbranch ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/12/logs/stdio
>
> - 13: pass .bunsen.source.gitrepo ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/13/logs/stdio
>
> - 14: upload to bunsen ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/14/logs/stdio
>
> - 15: clean up ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/15/logs/stdio
>
> - 16: rm -rf binutils-build_1 ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/1218/steps/16/logs/stdio
>
next prev parent reply other threads:[~2022-12-23 22:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 21:30 builder
2022-12-23 22:10 ` Indu Bhagat [this message]
2022-12-24 1:46 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 1:09 builder
2022-11-16 3:50 ` Indu Bhagat
2022-11-02 2:50 builder
2022-11-02 3:06 ` Jiang, Haochen
[not found] <20221019073533.3F8543858D3C@sourceware.org>
2022-10-19 7:55 ` Tom de Vries
2022-10-19 9:02 ` Alan Modra
2022-10-19 7:35 builder
2022-10-11 12:35 builder
2022-09-28 1:23 builder
2022-09-28 0:20 builder
2022-09-27 3:09 builder
2022-09-26 15:57 builder
2022-09-22 7:49 builder
2022-09-19 0:37 builder
2022-09-07 0:32 builder
2022-07-25 0:24 builder
2022-07-19 1:32 builder
2022-07-03 16:54 builder
2022-07-03 17:30 ` Mark Wielaard
2022-05-25 15:27 builder
2022-05-25 19:11 ` 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=f9770b56-42a4-c70c-d7dd-c772648921ef@oracle.com \
--to=indu.bhagat@oracle.com \
--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).