public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Thu, 26 May 2022 15:15:14 +0200	[thread overview]
Message-ID: <Yo99Ytgnoi5WO2jf@wildebeest.org> (raw)
In-Reply-To: <20220526095341.1E3D3383941F@sourceware.org>

Hi,

On Thu, May 26, 2022 at 09:53:41AM +0000, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-fedora-s390x while building gccrust.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/37/builds/136
> 
> Build state: failed 'grep unexpected ...' (failure)
> Revision: 4cfd6942c07021db05beae40e1128901e37109e6
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: Philip Herron <philip.herron@embecosm.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/1/logs/stdio
> 
> - 2: rm -rf gccrs-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/2/logs/stdio
> 
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/3/logs/stdio
> 
> - 4: make ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/4/logs/stdio
>         - warnings (54): https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/4/logs/warnings__54_
> 
> - 5: make check ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/5/logs/stdio
>         - rust.sum: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/5/logs/rust_sum
>         - rust.log: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/5/logs/rust_log
>         - warnings (4): https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/5/logs/warnings__4_
> 
> - 6: grep unexpected rust.sum ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/37/builds/136/steps/6/logs/stdio

Note the FAILs are in the stdio log, but not (???) in the rust.sum or
rust.log files. I don't understand why yet:

FAIL: rust/execute/torture/builtin_macros1.rs   -O0  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -O1  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -O2  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -O3 -g  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -Os  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -O2 -flto -fno-use-linker-plugin -flto-partition=none  output pattern test
FAIL: rust/execute/torture/builtin_macros1.rs   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  output pattern test

They only seem to fail on s390x.
https://builder.sourceware.org/buildbot/#/changes/1458

Cheers,

Mark


  reply	other threads:[~2022-05-26 13:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  9:53 builder
2022-05-26 13:15 ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09 11:17 builder
2022-12-07 15:50 builder
2022-12-07 15:47 builder
2022-11-30 10:53 builder
2022-11-07 14:09 builder
2022-10-27 19:59 builder
2022-10-26 16:25 builder
2022-10-21 16:03 builder
2022-09-30 16:21 builder
2022-09-27  7:02 builder
2022-09-27  6:49 builder
2022-08-31 10:44 builder
2022-08-25 16:37 builder
2022-08-22 15:30 builder
2022-08-19 15:07 builder
2022-08-17 12:54 builder
2022-08-09 15:36 builder
2022-08-09 15:33 builder
2022-08-09 14:53 builder
2022-08-05 13:57 builder
2022-08-05 10:37 builder
2022-08-04 20:34 builder
2022-07-22 11:58 builder
2022-07-15 17:46 builder
2022-07-15 19:18 ` Mark Wielaard
2022-07-07 10:34 builder
2022-06-01  9:33 builder
2022-05-19 10:43 builder
2022-05-11 18:06 builder
2022-05-11 18:30 ` Mark Wielaard
2022-05-10 18:05 builder
2022-05-10 11:00 builder
2022-05-10 11:38 ` Mark Wielaard
2022-05-10 12:18 ` dkm
2022-05-09 11:33 builder
2022-04-28 19:48 builder

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=Yo99Ytgnoi5WO2jf@wildebeest.org \
    --to=mark@klomp.org \
    --cc=gcc-rust@gcc.gnu.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).