On Fri, 13 Sept 2024 at 15:55, Jason Merrill jason@redhat.com wrote:
On 9/12/24 9:13 PM, 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 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-1342 , 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-3608-gc5009eb88791 | Author: Jason Merrill jason@redhat.com | Date: Tue Aug 27 13:15:16 2024 -0400 | | libcpp: adjust pedwarn handling | | Using cpp_pedwarning (CPP_W_PEDANTIC instead of if (CPP_PEDANTIC cpp_error | lets users suppress these diagnostics with | #pragma GCC diagnostic ignored "-Wpedantic". | | This patch changes all instances of the cpp_error (CPP_DL_PEDWARN to | ... 44 lines of the commit log omitted.
FAIL: 4 regressions
regressions.sum: === g++ tests ===
Running g++:g++.dg/dg.exp ... FAIL: c-c++-common/pragma-diag-17.c -std=gnu++14 (test for excess errors) FAIL: c-c++-common/pragma-diag-17.c -std=gnu++17 (test for excess errors) FAIL: c-c++-common/pragma-diag-17.c -std=gnu++98 (test for excess errors) === gcc tests ===
Running gcc:gcc.dg/dg.exp ... FAIL: c-c++-common/pragma-diag-17.c -Wc++-compat (test for excess errors) ... and 1 more entries
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements 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_gcc_check master-arm
-----------------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/2697/artifact/art... Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2696/artifact/art...
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/c5009eb887910271ea35a857aa68941c722...
List of configurations that regressed due to this commit :
- tcwg_gcc_check
** master-arm *** FAIL: 4 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha... *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2697/artifact/art...
Curious, does this resolve the problems?
Hi,
I think you forgot to attach a patch or a pointer to a patch?
Anyway, these failures do not appear anymore, likely fixed by https://gcc.gnu.org/git/?p=gcc.git%3Ba=commit%3Bh=49cb7150f0e93e8332f4b78753...
Thanks,
Christophe
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org