From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (Sourceware): gccrust - failed '! grep ...' (failure) (master)
Date: Fri, 18 Aug 2023 18:17:51 +0200 [thread overview]
Message-ID: <752bc6de9838cd8f009443458dde241a63662cf6.camel@klomp.org> (raw)
In-Reply-To: <20230818160704.BC2383860765@sourceware.org>
Hi,
On Fri, 2023-08-18 at 16:07 +0000, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-debian-ppc64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/3/builds/1488
>
> Build state: failed '! grep ...' (failure)
> Revision: b1dd53faa1aa9ebd935742e57166647c055bae2a
> Worker: debian-ppc64
So, this is "expected", the buildbot step is now more clear:
> - 6: grep FAIL or unexpected rust.sum ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/1488/steps/6/logs/stdio
This now shows:
FAIL: rust/compile/builtin_macro_eager1.rs scan-tree-dump-times gimple ""test1canary"" 1
FAIL: rust/compile/builtin_macro_recurse2.rs scan-tree-dump-times gimple ""abheyho"" 1
FAIL: rust/compile/const-issue1440.rs at line 52 (test for errors, line 51)
FAIL: rust/compile/const-issue1440.rs at line 64 (test for errors, line 63)
FAIL: rust/compile/const-issue1440.rs (test for excess errors)
FAIL: rust/compile/issue-1446.rs (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O0 (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O1 (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O2 (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O3 -g (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -Os (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors)
# of unexpected failures 13
> - 15: upload to bunsen ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/3/builds/1488/steps/15/logs/stdio
Also note that this step now shows the bunsen URL, which contains the
full testsuite logs:
https://builder.sourceware.org/testrun/ea54c760540e4fcb425d55a8da3b10cc77baa0b6
Look under the dejagnu tab, you can click through to the actual FAILs
in the .exp file and then get the log for an specific test. e.g. for
issue-1446.rs see:
https://builder.sourceware.org/testrun/ea54c760540e4fcb425d55a8da3b10cc77baa0b6?filename=gcc%2Ftestsuite%2Frust%2Frust.log&fileline=1817&linewindow=20#line1817
Cheers,
Mark
next prev parent reply other threads:[~2023-08-18 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 16:07 builder
2023-08-18 16:17 ` Mark Wielaard [this message]
2023-09-03 0:23 builder
2023-09-04 9:54 builder
2023-09-07 19:32 builder
2023-09-11 16:21 builder
2023-10-26 17:12 builder
2024-02-03 18:39 builder
2024-04-11 5:40 builder
2024-04-11 20:02 builder
2024-04-11 20:04 builder
2024-04-11 20:05 builder
2024-04-11 20:31 builder
2024-04-11 23:23 builder
2024-04-11 23:40 builder
2024-04-11 23:54 builder
2024-04-12 4:27 builder
2024-04-12 4:59 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=752bc6de9838cd8f009443458dde241a63662cf6.camel@klomp.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).