public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: ci_notify@linaro.org
To: jakub@redhat.com
Cc: gcc-regression@gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-14-10092-gf9940945927: FAIL: 2 regressions on arm
Date: Tue, 23 Apr 2024 17:43:09 +0000 (UTC)	[thread overview]
Message-ID: <59086212.26139.1713894191307@jenkins.jenkins> (raw)

[-- Attachment #1: Type: text/plain, Size: 3134 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-1204 , 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-14-10092-gf9940945927
  | Author: Jakub Jelinek <jakub@redhat.com>
  | Date:   Tue Apr 23 14:51:26 2024 +0200
  | 
  |     Further spelling fixes in translatable strings
  |     
  |     This addresses the non-Oxford British English vs. US English spelling
  |     nits in translatable strings.
  |     
  |     I see various similar cases in m2 and rust FEs where they don't make it into
  |     gcc.pot, guess those would be nice to get fixed too.
  | ... 9 lines of the commit log omitted.

FAIL: 2 regressions

regressions.sum:
		=== objc tests ===

Running objc:objc.dg/attributes/attributes.exp ...
FAIL: objc.dg/attributes/nullability-00.m -fgnu-runtime  (test for errors, line 11)
FAIL: objc.dg/attributes/nullability-00.m -fgnu-runtime (test for excess errors)


You can find the failure logs in *.log.1.xz files in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2013/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_gcc_check--master-arm-build/2013/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2013/artifact/artifacts/sumfiles/xfails.xfail

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/2013/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2012/artifact/artifacts

Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/f99409459270831685f043987f8d09b9510ccabe/tcwg_gcc_check/master-arm/reproduction_instructions.txt

Full commit : https://github.com/gcc-mirror/gcc/commit/f99409459270831685f043987f8d09b9510ccabe

List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-arm
*** FAIL: 2 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/f99409459270831685f043987f8d09b9510ccabe/tcwg_gcc_check/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2013/artifact/artifacts

                 reply	other threads:[~2024-04-23 17:43 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=59086212.26139.1713894191307@jenkins.jenkins \
    --to=ci_notify@linaro.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=jakub@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).