public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Fri, 15 Jul 2022 21:18:25 +0200	[thread overview]
Message-ID: <YtG9gZHHzZ67k+OG@wildebeest.org> (raw)
In-Reply-To: <20220715174642.02F303857BBF@sourceware.org>

Hi,

On Fri, Jul 15, 2022 at 05:46:42PM +0000, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-rawhide-x86_64 while building gccrust.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/132/builds/38
> 
> Build state: failed 'grep unexpected ...' (failure)
> Revision: 2d1378f7310be651e2a538f192d385b136b3d697
> Worker: bb2
> Build Reason: (unknown)
> Blamelist: Philip Herron <philip.herron@embecosm.com>
> 
> Steps:
>
> - 5: make check ( warnings )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/stdio
>         - rust.sum: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_sum
>         - rust.log: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/rust_log
>         - warnings (8): https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/5/logs/warnings__8_

Oddly the rust.log doesn't contain the FAILed tests.

> - 14: upload to bunsen ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/132/builds/38/steps/14/logs/stdio

Luckily the upload does contain the bunsen link:
https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e

Which contain the full rust.log file (under filelist):
https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e?filename=gcc%2Ftestsuite%2Frust%2Frust.log

PASS: rust/execute/torture/match1.rs   -O2 -flto -fno-use-linker-plugin -flto-partition=none  execution test
PASS: rust/execute/torture/match1.rs   -O2 -flto -fno-use-linker-plugin -flto-partition=none  output pattern test
Executing on host: /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../gccrs -B/home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../  /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs/gcc/testsuite/rust/execute/torture/match1.rs   -fdiagnostics-plain-output     -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects     -lm  -o ./match1.exe    (timeout = 10)
spawn -ignore SIGHUP /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../gccrs -B/home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs-build/gcc/testsuite/rust1/../../ /home/builder/shared/fedora-rawhide/worker/gccrust-rawhide-x86_64/gccrs/gcc/testsuite/rust/execute/torture/match1.rs -fdiagnostics-plain-output -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -lm -o ./match1.exe
WARNING: program timed out
compiler exited with status 1
FAIL: rust/execute/torture/match1.rs   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  (test for excess errors)
Excess errors:
exit status is 1
Setting LD_LIBRARY_PATH to .:.:
Execution timeout is: 300
FAIL: rust/execute/torture/match1.rs   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  execution test

This is odd. The -fno-fat-lto-objects variant is the only failure. But
other builds with -fno-fat-lto-objects PASS:
https://builder.sourceware.org/testrun/4089d04b3ec71f873716bdac207b31ec43a1e00e?dgexpfile=rust%2Fexecute%2Ftorture%2Fexecute.exp

Also all other arches/distros passed (except s390x of course):
https://builder.sourceware.org/buildbot/#/changes/3381

The rawhide builder should not really be slower than other
builders. So I am not sure why it timed out but others didn't.

Cheers,

Mark


  reply	other threads:[~2022-07-15 19:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 17:46 builder
2022-07-15 19:18 ` 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-07 10:34 builder
2022-06-01  9:33 builder
2022-05-26  9:53 builder
2022-05-26 13:15 ` Mark Wielaard
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=YtG9gZHHzZ67k+OG@wildebeest.org \
    --to=mark@klomp.org \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=philip.herron@embecosm.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).