Hi David,
As you have probably guessed, this is a false alarm: the testcases you updated were already failing before your patch, but it changed the line numbers, thus making the scripts think a failure disappeared and a new one appeared.
Thanks,
Christophe
On Mon, 8 Jan 2024 at 01:15, 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-1094 , please let us know if you are looking at the problem and/or when you have a fix.
In bootstrap_check master-arm-check_bootstrap_lto after:
| commit gcc-14-6840-g86f535cb466 | Author: David Edelsohn dje.gcc@gmail.com | Date: Tue Dec 26 16:44:09 2023 +0000 | | testsuite: Skip analyzer out-of-bounds-diagram on AIX. | | The out-of-bounds diagram tests fail on AIX. | | gcc/testsuite/ChangeLog: | * gcc.dg/analyzer/out-of-bounds-diagram-17.c: Skip on AIX. | * gcc.dg/analyzer/out-of-bounds-diagram-18.c: Same. | ... 2 lines of the commit log omitted.
FAIL: 2 regressions: 2 progressions
regressions.sum: === gcc tests ===
Running gcc:gcc.dg/analyzer/analyzer.exp ... FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 15-36 FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 15-44
=== Results Summary ===progressions.sum: === gcc tests ===
Running gcc:gcc.dg/analyzer/analyzer.exp ... FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 14-35 FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 14-43
=== Results Summary ===You can find the failure logs in *.log.1.xz files in
The full lists of regressions and progressions are in
The list of [ignored] baseline and flaky failures are in
The configuration of this build is: CI config tcwg_bootstrap_check master-arm-check_bootstrap_lto
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_l... Reference build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_l...
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/86f535cb4664fcaf96ff12942887db949be...
List of configurations that regressed due to this commit :
- tcwg_bootstrap_check
** master-arm-check_bootstrap_lto *** FAIL: 2 regressions: 2 progressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha... *** https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_l...