public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: ci_notify@linaro.org
To: jwakely@redhat.com
Cc: gcc-regression@gcc.gnu.org
Subject: [Linaro-TCWG-CI] basepoints/gcc-14-4056-g7810fb3a142: FAIL: 6 regressions: 3 progressions
Date: Sat, 16 Sep 2023 14:25:00 +0000 (UTC) [thread overview]
Message-ID: <191613815.16806.1694874301944@jenkins.jenkins> (raw)
[-- Attachment #1: Type: text/plain, Size: 3330 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.
In CI config tcwg_gcc_check/master-arm after:
| commit basepoints/gcc-14-4056-g7810fb3a142
| Author: Jonathan Wakely <jwakely@redhat.com>
| Date: Fri Sep 1 21:28:05 2023 +0100
|
| libstdc++: Remove dg-options "-std=gnu++23" from remaining tests
|
| The testsuite will automatically select C++23 for these tests now, and
| removing the hardcoded -std option allows them to be tested for C++26
| as well.
|
| libstdc++-v3/ChangeLog:
| ... 128 lines of the commit log omitted.
FAIL: 6 regressions: 3 progressions
regressions.sum:
=== libstdc++ tests ===
Running libstdc++:libstdc++-dg/conformance.exp ...
FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 execution test
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test
FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++23 execution test
FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test
... and 1 more entries
progressions.sum:
=== libstdc++ tests ===
Running libstdc++:libstdc++-dg/conformance.exp ...
FAIL: 19_diagnostics/stacktrace/current.cc execution test
FAIL: 19_diagnostics/stacktrace/entry.cc execution test
FAIL: 19_diagnostics/stacktrace/stacktrace.cc execution test
=== Results Summary ===
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1023/artifact/artifacts/00-sumfiles/ .
The full lists of regressions and progressions are in
- https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1023/artifact/artifacts/notify/ .
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1023/artifact/artifacts/sumfiles/xfails.xfail .
-----------------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/1023/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1022/artifact/artifacts
Reproduce last good and first bad builds: https://git.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/7810fb3a142bed6da9eca8fde114629023fc5c4e/tcwg_gcc_check/master-arm/reproduction_instructions.txt
Full commit : https://github.com/gcc-mirror/gcc/commit/7810fb3a142bed6da9eca8fde114629023fc5c4e
Latest bug report status : https://linaro.atlassian.net/browse/GNU-943
List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-arm
*** FAIL: 6 regressions: 3 progressions
*** https://git.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/7810fb3a142bed6da9eca8fde114629023fc5c4e/tcwg_gcc_check/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1023/
reply other threads:[~2023-09-16 14:25 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=191613815.16806.1694874301944@jenkins.jenkins \
--to=ci_notify@linaro.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=linaro-toolchain@lists.linaro.org \
/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: link
Be 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).