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
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

Reply via email to