public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: ci_notify@linaro.org To: ppalka@redhat.com Cc: gcc-regression@gcc.gnu.org Subject: [Linaro-TCWG-CI] gcc-14-9374-gf5c1224708a: FAIL: 15 regressions: 15 progressions on aarch64 Date: Sat, 9 Mar 2024 10:36:18 +0000 (UTC) [thread overview] Message-ID: <1727964680.12527.1709980579415@jenkins.jenkins> (raw) [-- Attachment #1: Type: text/plain, Size: 4985 bytes --] 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-1172 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit gcc-14-9374-gf5c1224708a | Author: Patrick Palka <ppalka@redhat.com> | Date: Thu Mar 7 16:39:20 2024 -0500 | | c++/modules: member alias tmpl partial inst [PR103994] | | Alias templates are weird in that their specializations can appear in | both decl_specializations and type_specializations. They're always in | the decl table, and additionally appear in the type table only at parse | time via finish_template_type. There seems to be no good reason for | them to appear in both tables, and the code paths end up stepping over | ... 55 lines of the commit log omitted. FAIL: 15 regressions: 15 progressions regressions.sum: === g++ tests === Running g++:g++.dg/modules/modules.exp ... FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6099) FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6099) ... and 9 more entries progressions.sum: === g++ tests === Running g++:g++.dg/modules/modules.exp ... FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) ... and 9 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1329/artifact/artifacts/00-sumfiles/ The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1329/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1329/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gnu_cross_check_gcc 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_cross_check_gcc--master-aarch64-build/1329/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1328/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/f5c1224708a0cf9cc2770c44bbbe7d0c883942be/tcwg_gnu_cross_check_gcc/master-aarch64/reproduction_instructions.txt Full commit : https://github.com/gcc-mirror/gcc/commit/f5c1224708a0cf9cc2770c44bbbe7d0c883942be List of configurations that regressed due to this commit : * tcwg_gnu_cross_check_gcc ** master-aarch64 *** FAIL: 15 regressions: 15 progressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/f5c1224708a0cf9cc2770c44bbbe7d0c883942be/tcwg_gnu_cross_check_gcc/master-aarch64/details.txt *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/1329/artifact/artifacts
reply other threads:[~2024-03-09 10:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1727964680.12527.1709980579415@jenkins.jenkins \ --to=ci_notify@linaro.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=linaro-toolchain@lists.linaro.org \ --cc=ppalka@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).