Hi,
ci_notify(a)linaro.org is sending test results to
gcc-restresults(a)gcc.gnu.org but recently starting to fail so many tests
that they don't get accepted anymore:
From: ci_notify(a)linaro.org on Tue Sep 10 02:17:32 2024
Subject: Results for 15.0.0 20240906 (experimental) [master revision
gcc-15-3512-ge8378231bb8] (GCC) testsuite on arm-unknown-eabi
Cause: Message body is too big: 6548864 bytes with a limit of 1000 KB
From: ci_notify(a)linaro.org on Tue Sep 10 05:28:38 2024
Subject: Results for 15.0.0 20240906 (experimental) [master revision
gcc-15-3512-ge8378231bb88] (GCC) testsuite on arm-unknown-eabi
Cause: Message body is too big: 6559111 bytes with a limit of 1000 KB
From: ci_notify(a)linaro.org on Tue Sep 10 10:55:10 2024
Subject: Results for 15.0.0 20240906 (experimental) [master revision
gcc-15-3512-ge8378231bb88] (GCC) testsuite on arm-unknown-eabi
Cause: Message body is too big: 6548861 bytes with a limit of 1000 KB
So that is 6.5MB of results. Almost all look like:
FAIL: 17_intro/freestanding.cc -std=gnu++17 (test for excess errors)
UNRESOLVED: 17_intro/freestanding.cc -std=gnu++17 compilation failed
to produce executable
Could someone take a look? It seems that the compiler is just crashing
on every test.
Thanks,
Mark
On Fri, 13 Sept 2024 at 07:09, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1344 , please let us know if you are looking at the problem and/or when you have a fix.
This should be fixed by
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662945.html
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-15-3614-g9fe57e4879de
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Sep 11 11:47:44 2024 +0100
> |
> | c++: Make __builtin_launder reject invalid types [PR116673]
> |
> | The standard says that std::launder is ill-formed for function pointers
> | and cv void pointers, so there's no reason for __builtin_launder to
> | accept them. This change allows implementations of std::launder to defer
> | to the built-in for error checking, although libstdc++ will continue to
> | diagnose it directly for more user-friendly diagnostics.
> | ... 12 lines of the commit log omitted.
>
> FAIL: 12 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++11 (test for errors, line 304)
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++11 (test for excess errors)
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++17 (test for errors, line 304)
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++17 (test for excess errors)
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++98 (test for errors, line 304)
> FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++98 (test for excess errors)
> FAIL: g++.dg/ext/sve-sizeless-2.C -std=gnu++11 (test for errors, line 304)
> ... and 6 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…
> The full lists of regressions and improvements as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2594/artifac…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/9fe57e4879de93b6e3c7b4c226f42d5f3a…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 12 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…
Hi Jason,
On Thu, 12 Sept 2024 at 00:15, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1339 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In arm-eabi cortex-m7 hard after:
>
> | commit gcc-15-3532-g7cebc6384a0a
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Fri Sep 6 15:28:53 2024 -0400
> |
> | c++: exception spec and stdlib specialization
> |
> | We were silently accepting the pr65923.C specialization of std::swap with
> | the wrong exception specification; it should be declared noexcept. Let's
> | limit ignoring mismatch with system headers to extern "C" functions so we
> | get a diagnostic for the C++ library.
> |
> | ... 18 lines of the commit log omitted.
>
> FAIL: 6 regressions: 6 improvements
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++17 (test for excess errors)
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++17 compilation failed to produce executable
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++20 (test for excess errors)
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++20 compilation failed to produce executable
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++26 (test for excess errors)
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++26 compilation failed to produce executable
>
>
> improvements.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++20 compilation failed to produce executable
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++26 compilation failed to produce executable
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++26 (test for excess errors)
> UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++17 compilation failed to produce executable
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++20 (test for excess errors)
> FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++17 (test for excess errors)
This is not a regression, these tests used to fail with -std=c++XX and
now they still fail with -std=gnuXX.
I guess this is the effect of adding 'dg-options ""' ?
And... the reason they fail to produce an executable is a recent patch
of mine in the linker, which should now be fixed.
Thanks,
Christophe
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
> The full lists of regressions and improvements as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7e-m+fp.dp -mtune=cortex-m7 -mfloat-abi=hard -mfpu=auto
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/7cebc6384a0ad63d444029472a8ed1afe9…
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_embed_check_gcc
> ** master-thumb_m7_eabi
> *** FAIL: 6 regressions: 6 improvements
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…
Hi Jakub,
On Tue, 10 Sept 2024 at 05:17, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1338 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In arm-eabi cortex-m3 softfp after:
>
> | commit gcc-15-3513-g964577c31df2
> | Author: Jakub Jelinek <jakub(a)redhat.com>
> | Date: Fri Sep 6 13:50:47 2024 +0200
> |
> | c++: Partially implement CWG 2867 - Order of initialization for structured bindings [PR115769]
> |
> | The following patch partially implements CWG 2867
> | - Order of initialization for structured bindings.
> | The DR requires that initialization of e is sequenced before r_i and
> | that r_i initialization is sequenced before r_j for j > i, we already do it
> | that way, the former ordering is a necessity so that the get calls are
> | ... 78 lines of the commit log omitted.
>
> FAIL: 12 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++11 (test for excess errors)
> UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++11 compilation failed to produce executable
> FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++14 (test for excess errors)
> UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++14 compilation failed to produce executable
> FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++17 (test for excess errors)
> UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++17 compilation failed to produce executable
> FAIL: g++.dg/DRs/dr2867-2.C -std=gnu++11 (test for excess errors)
> ... and 6 more entries
These errors in the new tests added by your patch are caused by a
recent patch of mine in binutils, for which I have sent a fix
proposal:
https://sourceware.org/pipermail/binutils/2024-September/136677.html
Thanks,
Christophe
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> The full lists of regressions and improvements as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7-m -mtune=cortex-m3 -mfloat-abi=softfp -mfpu=auto
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/964577c31df206d780d5cc7bc07189d44d…
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_embed_check_gcc
> ** master-thumb_m3_softfp_eabi
> *** FAIL: 12 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
On Mon, Sep 09, 2024 at 12:37:30PM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1343 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_kernel/llvm-master-aarch64-next-allmodconfig after:
>
> | commit v6.10-12615-g08c2182cf0b47
> | Author: Florian Westphal <fw(a)strlen.de>
> | Date: Tue Aug 27 15:37:32 2024 +0200
> |
> | xfrm: policy: use recently added helper in more places
> |
> | No logical change intended.
> |
> | Signed-off-by: Florian Westphal <fw(a)strlen.de>
> | Signed-off-by: Steffen Klassert <steffen.klassert(a)secunet.com>
Thanks for the report, I'll ping my fix for this now:
https://lore.kernel.org/all/20240829-xfrm-restore-dir-assign-xfrm_hash_rebu…
Cheers,
Nathan
ci_notify(a)linaro.org writes:
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1334 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In master-aarch64 after:
>
> | commit gdb-15-branchpoint-893-gdcaa85e58c4
> | Author: Andrew Burgess <aburgess(a)redhat.com>
> | Date: Wed May 1 10:47:47 2024 +0100
> |
> | gdb: reject inserting breakpoints between functions
> |
> | When debugging ROCm code, you might have something like this:
> |
> | __global__ void kernel ()
> | {
> | ...
> | ... 153 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === gdb tests ===
>
> Running gdb:gdb.go/max-depth.exp ...
> FAIL: gdb.go/max-depth.exp: gdb_breakpoint: set breakpoint at 38
There's something a little weird going on here, in the log I see:
(gdb) run
Starting program: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gdb-gdb.git~master/gdb/testsuite/outputs/gdb.go/max-depth/max-depth
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gdb-gdb.git~master/gdb/testsuite/outputs/gdb.go/max-depth/max-depth: error while loading shared libraries: libgo.so.23: cannot open shared object file: No such file or directory
[Inferior 1 (process 908724) exited with code 0177]
(gdb) FAIL: gdb.go/max-depth.exp: runto: run to main.main
break 38
No compiled code for line 38 in the current file.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) FAIL: gdb.go/max-depth.exp: gdb_breakpoint: set breakpoint at 38
So it looks like the libgo.so.23 is missing from the test machine which
stop the inferior from running.
That said, I'd still expect GDB to place a b/p on line 38, and indeed,
when run on my local machine the b/p is placed correctly. But also, I
have the correct libraries in place so the inferior starts correctly...
Is it possible to see the gdb.log for the working world before this
patch was applied? It would be nice to confirm that despite failing to
start the inferior, GDB did manage to place the b/p correctly before
this patch.
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
I did wonder if the log file I wanted was one of these, but without
better descriptions it's hard to know what all these log files actually
are.
Thanks,
Andrew
> The full lists of regressions and improvements as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
>
> The configuration of this build is:
> CI config tcwg_gnu_native_check_gdb master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh…
>
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=dcaa85e58c4ef…
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_native_check_gdb
> ** master-aarch64
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1329 , please let us know if you are looking at the problem and/or when you have a fix.
In arm-eabi cortex-m33 hard after:
| commit binutils-2_41-release-4187-g31ed3a9d691
| Author: Christophe Lyon <christophe.lyon(a)linaro.org>
| Date: Wed Jun 19 12:35:30 2024 +0000
|
| arm: Do not insert stubs needing Arm code on Thumb-only cores.
|
| We recently fixed a bug in libgcc
| (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115360)
| where a symbol was missing a %function .type decoration.
|
| This meant the linker would silently pick the wrong type of 'farcall
| ... 48 lines of the commit log omitted.
FAIL: 72074 regressions: 94 improvements
regressions.sum:
=== g++ tests ===
Running g++:g++.dg/analyzer/analyzer.exp ...
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++26 (test for excess errors)
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++98 (test for excess errors)
Running g++:g++.dg/compat/compat.exp ...
FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link
FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o link
... and 72156 more entries
improvements.sum:
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++98 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++17 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++26 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++98 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++26 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++17 execution test
=== gcc tests ===
... and 104 more entries
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
The full lists of regressions and improvements as well as configure and make commands are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
The configuration of this build is:
CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=31ed3a9d69149…
List of configurations that regressed due to this commit :
* tcwg_gnu_embed_check_gcc
** master-thumb_m33_hard_eabi
*** FAIL: 72074 regressions: 94 improvements
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
*** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…