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…
On Wed, Sep 04, 2024 at 10:36:41PM +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-1339 , 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-allyesconfig after:
>
> | commit v6.11-rc1-143-g4e7795eda4459
> | Author: Kent Overstreet <kent.overstreet(a)linux.dev>
> | Date: Sun Sep 1 18:08:25 2024 -0400
> |
> | bcachefs: bch2_sb_member_alloc()
> |
> | refactoring
> |
> | Signed-off-by: Kent Overstreet <kent.overstreet(a)linux.dev>
Thanks for the report, this should be fixed now:
https://git.kernel.org/next/linux-next/c/da6e6a70084d99d522058bbef00b9cbe48…
Cheers,
Nathan
Hi,
Can I get a reduced .ll showing the regression, or some reduced steps for
reproducing the bug? I suspect the bug is elsewhere, and not in the commit
itself.
Warm regards,
Ram
On Thu, Sep 5, 2024 at 3:39 AM <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-1340 , please let us know if you
> are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla after:
>
> | commit llvmorg-20-init-4622-g16900d3b98e6
> | Author: Ramkumar Ramachandra <ramkumar.ramachandra(a)codasip.com>
> | Date: Wed Sep 4 22:01:04 2024 +0100
> |
> | LICM: hoist BO assoc when BinOp is in RHS (#107072)
> |
> | Extend hoistBOAssociation smoothly to handle the case when the
> inner
> | BinaryOperator is in the RHS of the outer BinaryOperator. This
> completes
> | the generalization of hoistBOAssociation, and the only limitation
> after
> | this patch is the fact that only Add and Mul are hoisted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === test-suite tests ===
>
> Running test-suite:Fujitsu/Fortran/0354 ...
> FAIL: test-suite :: Fujitsu/Fortran/0354/Fujitsu-Fortran-0354_0334.test
>
>
> You can find the failure logs in *.log.1.xz files in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> The configuration of this build is:
> CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Reproduce last good and first bad builds:
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit :
> https://github.com/llvm/llvm-project/commit/16900d3b98e6c8fbdad4411a054e356…
>
> List of configurations that regressed due to this commit :
> * tcwg_flang_test
> ** main-aarch64-Ofast-sve_vla
> *** FAIL: 1 regressions
> ***
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
> ***
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
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 appreciate 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-1324 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig after:
| commit gcc-15-3256-g1c4b9826bd0
| Author: Filip Kastl <fkastl(a)suse.cz>
| Date: Wed Aug 28 15:47:44 2024 +0200
|
| gimple ssa: switchconv: Use __builtin_popcount and support more types in exp transform [PR116355]
|
| The gen_pow2p function generates (a & -a) == a as a fallback for
| POPCOUNT (a) == 1. Not only is the bitmagic not equivalent to
| POPCOUNT (a) == 1 but it also introduces UB (consider signed
| a = INT_MIN).
|
| ... 43 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
9328
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
9330
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
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/1c4b9826bd0d5ac471543c68f097d80b19…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-lts-defconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
* ci notify:
> 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.
>
> In glibc_check master-arm after:
>
> | 4 patches in glibc
> | Patchwork URL: https://patchwork.sourceware.org/patch/96984
> | 11d52d986b elf: Reorder audit events in dlcose to match _dl_fini (bug 32066)
> | 7b2cd1e545 elf: Call la_objclose for proxy link maps in _dl_fini (bug 32065)
> | 0f79eb4a6f elf: Signal la_objopen for the proxy link map in dlmopen (bug 31985)
> | f26a9b6323 elf: Always write audit log to elf/tst-audit23.out
> | ... applied on top of baseline commit:
> | 96d0bf98ca Add support/ code for checking file contents
>
> FAIL: 1 regressions
>
> regressions.sum:
> === glibc tests ===
>
> Running glibc:elf ...
> FAIL: elf/tst-audit23
Adhemerval, does elf/tst-audit23.out now show more details?
Thanks,
Florian