From: Mark Wielaard <mark@klomp.org>
To: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Sun, 3 Jul 2022 19:30:34 +0200 [thread overview]
Message-ID: <YsHSOjRnAoaS00E/@wildebeest.org> (raw)
In-Reply-To: <20220703165422.40CA93843879@sourceware.org>
Hi,
On Sun, Jul 03, 2022 at 04:54:22PM +0000, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-rawhide-x86_64 while building binutils-gdb.
This wasn't becuase of a binutils source change and also not for
enabling the libctf checks. It seems to be caused by some rawhide
package update.
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/133/builds/9
>
> Build state: failed test (failure)
> Revision: dcc9b683dc7d6b0c8e64bfa5e11cf0830387bb31
> Worker: bb1
> Build Reason: (unknown)
> Blamelist: GDB Administrator <gdbadmin@sourceware.org>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/1/logs/stdio
>
> - 2: rm -rf binutils-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/3/logs/stdio
>
> - 4: make ( warnings )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/4/logs/stdio
> - warnings (64): https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/4/logs/warnings__64_
>
> - 5: make check ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/5/logs/stdio
> - ld.sum: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/5/logs/ld_sum
> - ld.log: https://builder.sourceware.org/buildbot/#builders/133/builds/9/steps/5/logs/ld_log
There are two failures:
FAIL: Run protected-data-1a without PIE
FAIL: Run protected-data-1b with PIE
ld.log says:
gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -I/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -g -O2 -c -g -O2 -fno-lto -fno-PIE -c /home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64/protected-data-1b.c -o tmpdir/protected-data-1b.o
Executing on host: sh -c {gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -I/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -g -O2 -c -g -O2 -fno-lto -fno-PIE -c /home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64/protected-data-1b.c -o tmpdir/protected-data-1b.o 2>&1} /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64 -L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib -L/usr/lib -o tmpdir/protected-data-1a -L/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -no-pie -Wl,--no-as-needed tmpdir/libprotected-data-1a.so tmpdir/protected-data-1b.o
Executing on host: sh -c {gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64 -L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib -L/usr/lib -o tmpdir/protected-data-1a -L/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -no-pie -Wl,--no-as-needed tmpdir/libprotected-data-1a.so tmpdir/protected-data-1b.o 2>&1} /dev/null ld.tmp (timeout = 300)
spawn [open ...]
Running: tmpdir/protected-data-1a > tmpdir/protected-data-1a.out
warning: copy relocation against non-copyable protected symbol `protected_data_1a' in `tmpdir/libprotected-data-1a.so'
FAIL: Run protected-data-1a without PIE
gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -I/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -g -O2 -c -g -O2 -fno-lto -fPIE -c /home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64/protected-data-1b.c -o tmpdir/protected-data-1b.o
Executing on host: sh -c {gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -I/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -g -O2 -c -g -O2 -fno-lto -fPIE -c /home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64/protected-data-1b.c -o tmpdir/protected-data-1b.o 2>&1} /dev/null ld.tmp (timeout = 300)
spawn [open ...]
gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64 -L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib -L/usr/lib -o tmpdir/protected-data-1b -L/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -Wl,--no-as-needed -pie tmpdir/libprotected-data-1a.so tmpdir/protected-data-1b.o
Executing on host: sh -c {gcc -B/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-build/ld/tmpdir/ld/ -L/usr/local/x86_64-pc-linux-gnu/lib64 -L/usr/local/lib64 -L/lib64 -L/usr/lib64 -L/usr/local/x86_64-pc-linux-gnu/lib -L/usr/local/lib -L/lib -L/usr/lib -o tmpdir/protected-data-1b -L/home/builder/shared/fedora-rawhide/worker/binutils-rawhide-x86_64/binutils-gdb/ld/testsuite/ld-x86-64 -Wl,--no-as-needed -pie tmpdir/libprotected-data-1a.so tmpdir/protected-data-1b.o 2>&1} /dev/null ld.tmp (timeout = 300)
spawn [open ...]
Running: tmpdir/protected-data-1b > tmpdir/protected-data-1b.out
warning: copy relocation against non-copyable protected symbol `protected_data_1a' in `tmpdir/libprotected-data-1a.so'
FAIL: Run protected-data-1b with PIE
The bunsen diff between the previous good run and this one:
https://builder.sourceware.org/testrun-diffs?commitish=55890dff74d1d3db4640697d2a29a2d14d784524&commitish=d368679c07c48ce5d3e7f25d5e891aaa4e3228b5
shows the same two FAILs, various new libctf test PASSes.
The ld/config.log files:
https://builder.sourceware.org/testrun/d368679c07c48ce5d3e7f25d5e891aaa4e3228b5?filename=ld%2Fconfig.log
https://builder.sourceware.org/testrun/55890dff74d1d3db4640697d2a29a2d14d784524?filename=ld%2Fconfig.log
Show a small update to GCC:
gcc version 12.1.1 20220507 (Red Hat 12.1.1-1) (GCC)
gcc version 12.1.1 20220628 (Red Hat 12.1.1-3) (GCC)
next prev parent reply other threads:[~2022-07-03 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 16:54 builder
2022-07-03 17:30 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-23 21:30 builder
2022-12-23 22:10 ` Indu Bhagat
2022-12-24 1:46 ` Mike Frysinger
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-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=YsHSOjRnAoaS00E/@wildebeest.org \
--to=mark@klomp.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).