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.her...@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

-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

Reply via email to