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, xndchn@gmail.com
Subject: [Linaro-TCWG-CI] gcc-14-9473-g0adc8c5f146: FAIL: 4 regressions on arm
Date: Sat, 16 Mar 2024 02:05:13 +0000 (UTC) [thread overview]
Message-ID: <980973835.18448.1710554714235@jenkins.jenkins> (raw)
[-- Attachment #1: Type: text/plain, Size: 3422 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-1178 , please let us know if you are looking at the problem and/or when you have a fix.
In master-arm_eabi after:
| commit gcc-14-9473-g0adc8c5f146
| Author: xndcn <xndchn@gmail.com>
| Date: Fri Feb 16 11:00:13 2024 +0000
|
| libstdc++: Add missing clear_padding in __atomic_float constructor
|
| For 80-bit long double we need to clear the padding bits on
| construction.
|
| libstdc++-v3/ChangeLog:
|
| ... 8 lines of the commit log omitted.
FAIL: 4 regressions
regressions.sum:
=== libstdc++ tests ===
Running libstdc++:libstdc++-dg/conformance.exp ...
FAIL: 29_atomics/atomic_float/compare_exchange_padding.cc -std=gnu++20 (test for excess errors)
UNRESOLVED: 29_atomics/atomic_float/compare_exchange_padding.cc -std=gnu++20 compilation failed to produce executable
FAIL: 29_atomics/atomic_float/compare_exchange_padding.cc -std=gnu++26 (test for excess errors)
UNRESOLVED: 29_atomics/atomic_float/compare_exchange_padding.cc -std=gnu++26 compilation failed to produce executable
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/620/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_embed_check_gcc--master-arm_eabi-build/620/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/620/artifact/artifacts/sumfiles/xfails.xfail
The configuration of this build is:
CI config tcwg_gnu_embed_check_gcc master-arm_eabi
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/620/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/619/artifact/artifacts
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/0adc8c5f146b108f99c4df09e43276e3a2419262/tcwg_gnu_embed_check_gcc/master-arm_eabi/reproduction_instructions.txt
Full commit : https://github.com/gcc-mirror/gcc/commit/0adc8c5f146b108f99c4df09e43276e3a2419262
List of configurations that regressed due to this commit :
* tcwg_gnu_embed_check_gcc
** master-arm_eabi
*** FAIL: 4 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/0adc8c5f146b108f99c4df09e43276e3a2419262/tcwg_gnu_embed_check_gcc/master-arm_eabi/details.txt
*** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/620/artifact/artifacts
reply other threads:[~2024-03-16 2:05 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=980973835.18448.1710554714235@jenkins.jenkins \
--to=ci_notify@linaro.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=linaro-toolchain@lists.linaro.org \
--cc=xndchn@gmail.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: 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).