On Fri, Nov 01, 2024 at 06:57:21AM +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.
All the logs seem to be truncated?
What kind of failure is this? Is it a problem on the builder?
Thanks,
-Andi
>
> 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 gcc_build master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/99988
> | Author: Andi Kleen <ak(a)gcc.gnu.org>
> | Date: Thu Oct 31 16:19:16 2024 -0700
> |
> | [PATCH] Enable autofdo bootstrap for lto/fortran
> |
> | When autofdo bootstrap support was originally implemented there were
> | issues with the LTO bootstrap, that is why it wasn't enabled
> | for them. I retested this now and it works on x86_64-linux.
> | ... 10 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | f8ae2cce23fc Support Intel AMX-MOVRS
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> 1
>
> The configuration of this build is:
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* --target aarch64-linux-gnu
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/13759/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2726/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
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-1403 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-aarch64 after:
| commit glibc-2.40.9000-287-g5c22fd25c15
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Fri Oct 25 15:21:48 2024 -0300
|
| math: Use exp2m1f from CORE-MATH
|
| The CORE-MATH implementation is correctly rounded (for any rounding mode)
| and shows better performance compared to the generic exp2m1f.
|
| ... 41 lines of the commit log omitted.
FAIL: 2 regressions
regressions.sum:
| === glibc tests ===
|
| Running glibc:math ...
| FAIL: math/test-float-exp2m1
| FAIL: math/test-float32-exp2m1
|
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=5c22fd25c15ff56583ca…
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-1401 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-aarch64 after:
| commit glibc-2.40.9000-286-g5fa89852fa1
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Fri Oct 25 15:21:47 2024 -0300
|
| math: Use exp10m1f from CORE-MATH
|
| The CORE-MATH implementation is correctly rounded (for any rounding mode)
| and shows better performance compared to the generic exp10m1f.
|
| ... 33 lines of the commit log omitted.
FAIL: 2 regressions
regressions.sum:
| === glibc tests ===
|
| Running glibc:math ...
| FAIL: math/test-float-exp10m1
| FAIL: math/test-float32-exp10m1
|
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2028/artif…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=5fa89852fa12fe56c315…
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-1398 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit v9.1.0-1163-ga3c3345cac
| Author: Akihiko Odaki <akihiko.odaki(a)daynix.com>
| Date: Tue Oct 29 12:54:43 2024 +0000
|
| scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing
|
| The arguments in MESONINTROSPECT are quoted with shlex.quote() so it
| must be parsed with shlex.split(). Otherwise the script will fail if
| the build directory has a character like "~" in it.
| ... 21 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
7
The configuration of this build is:
*CI config* tcwg_gnu_cross_build master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/888/ar…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/887/ar…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/a3c3345cac7d2f9cc827d7ecce91579…
On Wed, Oct 30, 2024 at 06:06:06AM +0000, ci_notify(a)linaro.org wrote:
> In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after:
>
> | commit llvmorg-20-init-10266-g71315698c91d
> | Author: serge-sans-paille <sguelton(a)mozilla.com>
> | Date: Mon Oct 28 20:40:52 2024 +0000
> |
> | [clang] Warn about memset/memcpy to NonTriviallyCopyable types (#111434)
> |
> | This implements a warning that's similar to what GCC does in that
> | context: both memcpy and memset require their first and second operand
> | to be trivially copyable, let's warn if that's not the case.
Thanks for the report, this should be fixed in tip of tree now:
https://github.com/llvm/llvm-project/commit/dc56a86b96d77a93f761995d50f7b2f…
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-1388 , please let us know if you are looking at the problem and/or when you have a fix.
Should be fixed with r15-4692-g40fedaf35fa99a9728d5b84d47035f4c92e1ba90.
thanks,
sam
Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
But the baseline file also has the same failure in sum file and somehow not shown in xfail file:
The list of [ignored] baseline and flaky failures are in
https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Thanks & Best Regards
Abdul Basit
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, October 26, 2024 4:29 AM
To: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
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 gdb_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582
| Author: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
| Date: Fri Oct 25 16:37:46 2024 +0200
|
| [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN
|
| Before this change resolve_dynamic_array_or_string was called for
| all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end,
| this function always called create_array_type_with_stride, which
| ... 65 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
|
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/artifact/ar…
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Fixed at r15-4720-ge320846fec00aa
On Mon, 28 Oct 2024 at 01:20, <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-1390 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-4709-gb281e13ecad1
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Oct 8 21:15:18 2024 +0100
> |
> | libstdc++: Add P1206R7 from_range members to std::vector [PR111055]
> |
> | This is another piece of P1206R7, adding new members to std::vector and
> | std::vector<bool>.
> |
> | ... 40 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++23 (test for excess errors)
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++26 (test for excess errors)
> |
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
> 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-arm-build/2927/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> -----------------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-arm-build/2927/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2926/artifact/ar…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b281e13ecad12d07209924a72…
Hi there!
These are legitimate regressions: the code compiled to bogus BIND(C) ABI that only worked when using with Fortran to Fortran. A TODO is now correctly emitted until the proper ABI is implemented.
In Fujitsu-Fortran-0379_0074
```
function strfunc() bind(C)
type,bind(C) :: str
integer :: iii
end type
type(str) :: strfunc
end function
end interface
type,bind(C) :: str
integer :: iii
end type
````
Previously, the result was passed in as a hidden extra argument, like it is done in normal Fortran ABI. On ARM, the equivalent C code is returned in registered as far as I can see: https://godbolt.org/z/nec6jbhYM
0384_0028.f90 also has BIND(C) function returning such BIND(C) types.
So, both tests should not be run on ARM, or should expect a TODO error message until the feature is implemented on ARM.
Jean
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Monday, October 14, 2024 11:23 PM
To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com
Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-8878-g367c3c968eb8: FAIL: 2 regressions on aarch64
External email: Use caution opening links or attachments
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-1398 , 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_vls-lto-lld after:
| commit llvmorg-20-init-8878-g367c3c968eb8
| Author: jeanPerier <jperier(a)nvidia.com>
| Date: Mon Oct 14 09:35:29 2024 +0200
|
| [flang] correctly deal with bind(c) derived type result ABI (#111969)
|
| Derived type results of BIND(C) function should be returned according
| the the C ABI for returning the related C struct type.
|
| ... 15 lines of the commit log omitted.
FAIL: 2 regressions
The configuration of this build is:
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : cmake -GNinja -DCMAKE_C_COMPILER="$WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite"
regressions.sum:
| === test-suite tests ===
|
| Running test-suite:Fujitsu/Fortran/0379 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0379/Fujitsu-Fortran-0379_0074.test
|
| Running test-suite:Fujitsu/Fortran/0384 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0028.test
|
| # "NOEXE" means : the test program cannot be compiled
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
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_vls-lto-l…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
-----------------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_vls-lto-l…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/367c3c968eb8f29b55fb8019b2464c7…
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-1377 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit v9.1.0-759-g07f0d32641e
| Author: Paolo Bonzini <pbonzini(a)redhat.com>
| Date: Thu Oct 3 16:28:43 2024 +0300
|
| Require meson version 1.5.0
|
| This is needed for Rust support.
|
| Signed-off-by: Paolo Bonzini <pbonzini(a)redhat.com>
| ... 3 lines of the commit log omitted.
The configuration of this build is:
CI config tcwg_gnu_cross_build master-aarch64
configure and test flags: --target aarch64-linux-gnu
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
7
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/854/ar…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/853/ar…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/07f0d32641e04703e6ed9626d061790…
Thanks for the report, I have opened
https://github.com/llvm/llvm-project/issues/111903 for this.
On Tue, Oct 08, 2024 at 07:40:22AM +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-1390 , 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-lts-allmodconfig after:
>
> | commit llvmorg-20-init-8119-gd2408c417cfa
> | Author: David Green <david.green(a)arm.com>
> | Date: Sun Oct 6 10:44:21 2024 +0100
> |
> | [InstCombine] Canonicalize more geps with constant gep bases and constant offsets. (#110033)
> |
> | This is another small but hopefully not performance negative step to
> | canonicalizing towards i8 geps. We looks for geps with a constant offset
> | base pointer of the form `gep (gep @glob, C1), x, C2` and expand the gep
> | ... 2 lines of the commit log omitted.
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 24511
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 33835
> # linux build successful:
> all
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/d2408c417cfa71f1786c90978856037…
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-1372 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit glibc-2.40.9000-232-gd40ac01cbbc
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Thu Oct 3 15:41:10 2024 -0300
|
| stdlib: Make abort/_Exit AS-safe (BZ 26275)
|
| The recursive lock used on abort does not synchronize with a new process
| creation (either by fork-like interfaces or posix_spawn ones), nor it
| is reinitialized after fork().
| ... 60 lines of the commit log omitted.
FAIL: 5 regressions
The configuration of this build is:
CI config tcwg_gnu_native_check_gdb master-aarch64
configure and test flags: --target aarch64-linux-gnu
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.reverse/waitpid-reverse.exp ...
| ERROR: GDB process no longer exists
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: check waitpid record
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: continue to breakpoint: marker2
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: reverse to marker1
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: set breakpoint at marker1
|
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…
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…
-----------------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…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d40ac01cbbc66e6d9dbd…
On Thu, 10 Oct 2024 at 06:33, <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-1370 , please let us know if you are looking at the problem and/or when you have a fix.
I'm not sure what the problem is here. It looks like the build uses
--enable-clocale=gnu and so I would expect the test to PASS on this
target, like it does on x86_64-pc-linux-gnu. Maybe it's a newlib vs
glibc difference. Looking into it ...
>
> In arm-eabi v7-a softfp after:
>
> | commit gcc-15-4016-gc534e37facc
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 24 23:20:56 2024 +0100
> |
> | libstdc++: Populate std::time_get::get's %c format for C locale
> |
> | We were using the empty string "" for D_T_FMT and ERA_D_T_FMT in the C
> | locale, instead of "%a %b %e %T %Y" as the C standard requires. Set it
> | correctly for each locale implementation that defines time_members.cc.
> | ... 18 lines of the commit log omitted.
>
> FAIL: 1 regressions
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
> configure and test flags: --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 22_locale/time_get/get/wchar_t/5.cc -std=gnu++17 execution test
> |
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_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-arm_v7a_softfp_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> -----------------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-arm_v7a_softfp_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/c534e37faccf481afa9bc28f0605ca0ec3…
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-1365 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-arm after:
| commit glibc-2.40.9000-226-g42c810c2cf3
| Author: Joseph Myers <josmyers(a)redhat.com>
| Date: Mon Oct 7 19:44:25 2024 +0000
|
| Add freopen special-case tests: thread cancellation
|
| Add tests of freopen adding or removing "c" (non-cancelling I/O) from
| the mode string (so completing my planned tests of freopen with
| different features used in the mode strings). Note that it's in the
| ... 5 lines of the commit log omitted.
FAIL: 1 regressions
The configuration of this build is:
CI config tcwg_glibc_check master-arm
configure and test flags: --target arm-linux-gnueabihf
regressions.sum:
| === glibc tests ===
|
| Running glibc:. ...
| FAIL: lint-makefiles
|
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1894/artifact/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=42c810c2cf3554afbdd6…
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-1379 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_flang_build/main-aarch64 after:
| commit llvmorg-20-init-8106-ge36a39346796
| Author: Matthias Springer <me(a)m-sp.org>
| Date: Sat Oct 5 21:46:31 2024 +0200
|
| [mlir][SPIRV] Fix build error (#111264)
|
| Fix build error that was introduced by #111250. Also, the deleted
| function is not needed at all.
|
| ... 9 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
1
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1063/artifac…
Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1062/artifac…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/e36a39346796528f75ff01ef1084b2d…
On Fri, Oct 04, 2024 at 07:05:02AM +0000, ci_notify(a)linaro.org wrote:
...
> | commit v6.11-rc4-291-g16531118ba63
> | Author: Denis Benato <benato.denis96(a)gmail.com>
> | Date: Sat Aug 24 16:11:22 2024 +0200
> |
> | iio: bmi323: peripheral in lowest power state on suspend
> |
> | The bmi323 is mounted on some devices that are powered
> | by an internal battery: help in reducing system overall power drain
> | while the system is in s2idle or the imu driver is not loaded
> | ... 5 lines of the commit log omitted.
This should be fixed with
https://git.kernel.org/jic23/iio/c/506a1ac4c4464a61e4336e135841067dbc040aaa
which is on its way for an -rc release.
Cheers,
Nathan
On Mon, 30 Sept 2024 at 07:22, <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-1358 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In arm-eabi cortex-m0 soft after:
>
> | commit gcc-15-3575-gc07cf418fdde
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 10 14:25:41 2024 +0100
> |
> | libstdc++: std::string move assignment should not use POCCA trait [PR116641]
> |
> | The changes to implement LWG 2579 (r10-327-gdb33efde17932f) made
> | std::string::assign use the propagate_on_container_copy_assignment
> | (POCCA) trait, for consistency with operator=(const basic_string&).
> | ... 18 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 (test for excess errors)
> | UNRESOLVED: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 compilation failed to produce executable
> |
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
=== libstdc++ Summary ===
# of expected passes 6036
# of unexpected failures 4689 <<< !!!
Is that normal for this configuration?!
The new testcase fails for the same reason as the 4000 other tests:
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(__deregister_frame_info): Unknown destination type (ARM/Thumb) in
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/./gcc/crtbegin.o
crtstuff.c:(.text+0x5e): dangerous relocation: unsupported relocation
So I don't think this is a problem in the commit, I think it's just a
configuration that isn't well supported.
> 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_m0_eabi-bu…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -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_m0_eabi-bu…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc72…
On 9/23/24 2:08 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.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/97864
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Mon Sep 23 11:06:11 2024 -0400
> |
> | libstdc++: #ifdef out #pragma GCC system_header
> |
> | Tested x86_64-pc-linux-gnu, OK for trunk?
> |
> | -- 8< --
> |
> | In r15-3714-gd3a7302ec5985a I added -Wsystem-headers to the libstdc++ build
> | ... 379 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 4700ad1c78c c++: diagnose this specifier in requires expr [PR116798]
>
> FAIL: 3 regressions
>
> regressions.sum:
> === libstdc++ tests ===
>
> Running libstdc++:libstdc++-dg/conformance.exp ...
> FAIL: 17_intro/headers/c++2011/parallel_mode.cc (test for excess errors)
> FAIL: 17_intro/headers/c++2014/parallel_mode.cc (test for excess errors)
> FAIL: 17_intro/headers/c++2017/parallel_mode.cc -std=gnu++17 (test for excess errors)
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/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-arm-precommit/9301/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifac…
Thanks, I believe
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663711.html
should fix this.
* 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:
>
> | 29 patches in glibc
> | Patchwork URL: https://patchwork.sourceware.org/patch/98131
> | 59fbaae3a6e Optimize various ways to obtain the page size using <bits/pagesize.h>
> | 564bcbe0067 posix: Use <support/next_to_fault.h> in tst-fnmatch3
> | 27a360de01d malloc: Use volatile as compiler barrier in tst-memalign, tst-valloc
> | e24dfc8d9a8 Linux: Optimize getpagesize using <sys/pagesize.h>
> | 3283915ffd0 Install the <sys/pagesize.h> header file
> | ... and 24 more patches in glibc
> | ... applied on top of baseline commit:
> | 6948ee4edf0 stdio-common: Fix memory leak in tst-freopen4* tests on UNSUPPORTED
>
> FAIL: 1 regressions
>
> regressions.sum:
> | === glibc tests ===
> |
> | Running glibc:elf ...
> | XPASS: elf/tst-load-alignment
Does this mean that the 32-bit arm tester uses a non-default toolchain
that increases page alignment to 64 KiB? With my cross-tester,
elf/tst-load-alignment fails as expected because the binaries can only
be loaded on 4 KiB page systems, based on the program header layout.
Thanks,
Florian
Hello,
a commit of mine seems to have broken your bot, but I am not sure how,
because it is a timeout:
https://lab.llvm.org/buildbot/#/builders/161/builds/2385.
The commit is
https://github.com/llvm/llvm-project/commit/e42cc3f42e6a36f4dfff40827819404…
and touches Clang's unit tests.
The build just before mine includes the previous commit of my own change,
and it was green, which points at that commit being the culprit here.
The commit brings in a custom command that generates
ASTMatchersDocTests.cpp in the build directory for inclusion in
the ASTMatchersTests unittest target/binary, but that target gets never
built, and the file never generated, according to the logs. I therefore
think that my changes to clang/unittests/ASTMatchers/ASTMatchersTest.h
should be the most likely to have cause this.
Do you have any experience with timeouts, or do you have/can acquire
additional information about what has timed out? I have left the commit
in-tree as clang-arm64-windows-msvc is the only bot I broke, and it is not
clear why. On the other hand, clang-x64-windows-msvc and the other Windows
bots are just fine, the same goes for other ARM but non-windows bots as
well.
Kind regards,
Julian Schmidt
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-1357 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit glibc-2.40.9000-213-gb300078d97a
| Author: Florian Weimer <fweimer(a)redhat.com>
| Date: Sat Sep 28 09:44:25 2024 +0200
|
| Linux: Block signals around _Fork (bug 32215)
|
| This hides the inconsistent TCB state (missing robust mutex list) from
| signal handlers.
|
| ... 1 lines of the commit log omitted.
FAIL: 4 regressions
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.base/step-over-syscall.exp ...
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork (timeout)
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: syscall number matches
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: find syscall insn in fork (timeout)
| FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: syscall number matches
|
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
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…
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…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b300078d97a6892cb2fa…
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-1356 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-15-3899-g819098dc71f2
> | Author: Sam James <sam(a)gentoo.org>
> | Date: Thu Sep 26 15:43:33 2024 +0100
> |
> | testsuite: XFAIL gfortran.dg/initialization_25.f90 properly
> |
> | The test was disabled/XFAIL'd informally in r0-100012-gcdc6637d7c78ec,
> | but r15-3890-g34bf6aa41ba539 didn't realize this, causing a FAIL.
> |
> | ... 7 lines of the commit log omitted.
>
> FAIL: 1 regressions: 1 improvements
>
Thanks, this is PR116858 and I'll handle it today or tomorrow at the
latest.
> regressions.sum:
> | === gfortran tests ===
> |
> | Running gfortran:gfortran.dg/dg.exp ...
> | FAIL: gfortran.dg/initialization_25.f90 -O xfail *-*-* (test for errors, line 11)
> |
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> improvements.sum:
> | === gfortran tests ===
> |
> | Running gfortran:gfortran.dg/dg.exp ...
> | FAIL: gfortran.dg/initialization_25.f90 -O (test for errors, line 11)
> |
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/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/2668/artifac…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/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/2668/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2667/artifac…
>
> Instruction to reproduce the build :
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/819098dc71f2079aedc15a904ab5f17f07…