A new failure has been detected on builder gccrust-debian-arm64 while building
gccrust.
Full details are available at:
https://builder.wildebeest.org/buildbot/#builders/58/builds/1807
Build state: failed compile (failure)
Revision: 46e0068fc0128207ac69bde5cb53d7eeb6943cbb
Worker: debian-arm6
A new failure has been detected on builder gccrust-debian-i386 while building
gccrust.
Full details are available at:
https://builder.wildebeest.org/buildbot/#builders/62/builds/1440
Build state: failed 'grep unexpected ...' (failure)
Revision: 4413bc0cf8b98702e8dd9e88ab5c0e19903e58e7
Worker
A new failure has been detected on builder gccrust-fedora-ppc64le while
building gccrust.
Full details are available at:
https://builder.wildebeest.org/buildbot/#builders/60/builds/1729
Build state: failed 'grep unexpected ...' (failure)
Revision: fed5a41fb1c2c91b77297fdd6d3731078f480441
Wor
For reference we found that the testsuite does timeout the test-case
and produces;
```
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/runner/work/gccrs
Hi everyone,
We merged a new builtin macro recently and during the code review we
missed a case where the code produces an infinite loop and so we
raised: https://github.com/Rust-GCC/gccrs/issues/1102
The GitHub CI did not seem to catch this issue, I am assuming dejagnu
timeout the test case and
