Hi Harald,
On Mon, 6 May 2024 at 21:02, ci_notify@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@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-1214 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit gcc-15-168-g21e7aa5f3ea | Author: Harald Anlauf anlauf@gmx.de | Date: Mon Apr 29 19:52:52 2024 +0200 | | Fortran: fix issues with class(*) assignment [PR114827] | | gcc/fortran/ChangeLog: | | PR fortran/114827 | * trans-array.cc (gfc_alloc_allocatable_for_assignment): Take into | account _len of unlimited polymorphic entities when calculating | ... 9 lines of the commit log omitted.
FAIL: 6 regressions
regressions.sum: === gfortran tests ===
Running gfortran:gfortran.dg/asan/asan.exp ... FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O0 execution test FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O1 execution test FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O2 execution test FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O3 -g execution test FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -Os execution test
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and progressions as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
The configuration of this build is: CI config tcwg_gnu_cross_check_gcc master-aarch64
Sorry for the delay in coming back to you regarding this notification. You can consider this as a false alarm, caused by the fact that the above configurations use QEMU, which is not (currently) compatible with LSAN (which is enabled by ASAN).
We are working on a fix in our testing framework to avoid such issues in the future.
Thanks,
Christophe
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/142... Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/142...
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha...
Full commit : https://github.com/gcc-mirror/gcc/commit/21e7aa5f3ea44ca2fef8deb8788edffc049...
List of configurations that regressed due to this commit :
- tcwg_gnu_cross_check_gcc
** master-aarch64 *** FAIL: 6 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha... *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/142...