From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Cc: nickc@redhat.com
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) test (failure) (master)
Date: Tue, 16 Apr 2024 17:36:18 +0200 [thread overview]
Message-ID: <255674f2bc8cd56006b4f3dc750588c5ef81f4f2.camel@klomp.org> (raw)
In-Reply-To: <20240416152239.B4E8D3858D35@sourceware.org>
Hi,
On Tue, 2024-04-16 at 15:22 +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder binutils-ubuntu-riscv while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/283/builds/367
>
> Build state: failed test (failure) test (failure)
> Revision: 3f6a060c7543332d0cb4377fc318e2db01ea1d3c
> Worker: starfive-2
> Build Reason: (unknown)
> Blamelist: [... way too many people ...]
Groan, sorry, it seems to be a real regression on riscv (in binutils).
But because ld did see failures before buildbot seems to get confused
who to "blame"...
This issue flagged is:
Executing on host: /var/lib/buildbot/workers/sourceware/binutils-
ubuntu-riscv/binutils-build/binutils/objcopy --preserve-dates
tmpdir/bintest tmpdir/copy (timeout = 300)
spawn -ignore SIGHUP /var/lib/buildbot/workers/sourceware/binutils-
ubuntu-riscv/binutils-build/binutils/objcopy --preserve-dates
tmpdir/bintest tmpdir/copy
cmp tmpdir/bintest tmpdir/copy
Executing on build: cmp tmpdir/bintest tmpdir/copy (timeout = 300)
spawn -ignore SIGHUP cmp tmpdir/bintest tmpdir/copy
tmpdir/bintest tmpdir/copy differ: char 73, line 1
tmpdir/bintest tmpdir/copy differ: char 73, line 1
FAIL: objcopy executable (pr25662)
Caused by:
commit 3f6a060c7543332d0cb4377fc318e2db01ea1d3c (HEAD -> master,
origin/master, origin/HEAD)
Author: Nick Clifton <nickc@redhat.com>
Date: Tue Apr 16 15:06:05 2024 +0100
Remove accidental commit of an experimental change
diff --git a/binutils/testsuite/binutils-all/pr25662.ld
b/binutils/testsuite/binutils-all/pr25662.ld
index 4951184f88ef..19ef1391f8d9 100644
--- a/binutils/testsuite/binutils-all/pr25662.ld
+++ b/binutils/testsuite/binutils-all/pr25662.ld
@@ -12,6 +12,4 @@ SECTIONS
.text : { *(.text) } > ROM
.bss : { *(.bss) } > RAM
-
- /DISCARD/ : { *(.*) }
}
So maybe this testcase accidentially succeeded on riscv, but was
supposed to fail?
Cheers,
Mark
next prev parent reply other threads:[~2024-04-16 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:22 builder
2024-04-16 15:36 ` Mark Wielaard [this message]
2024-04-16 15:45 ` Nick Clifton
2024-04-16 15:54 ` Palmer Dabbelt
2024-04-16 16:23 ` Nick Clifton
2024-04-16 17:36 ` Palmer Dabbelt
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=255674f2bc8cd56006b4f3dc750588c5ef81f4f2.camel@klomp.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).