Bad testcase
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 our CI doesn't pick this up as a failure and so I have pushed a patch directly to master to disable the offending test case. I am raising this here just for transparency for why I pushed to master and I hope the build farm is ok it might be worth cancelling any existing builds and letting them pick up the next merge's to master. For reference I pushed this patch to silence the issue: 68458036c81d141a3899ac4e6ec6ddf0fdfde174 Hope everyone is having a great start of the week. --Phil -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
Re: Bad testcase
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/gccrs/gcc/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running /home/runner/work/gccrs/gccrs/gcc/testsuite/rust/compile/compile.exp ...
max length for a Tcl unicode value (2147483637 chars) exceeded
/bin/bash: line 21: 92574 Aborted (core dumped) `if [ -f
${srcdir}/../dejagnu/runtest ] ; then echo
${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool rust
make[2]: Leaving directory '/home/runner/work/gccrs/gccrs/gccrs-build/gcc'
make[1]: Leaving directory '/home/runner/work/gccrs/gccrs/gccrs-build/gcc'
```
It's a pity make check-rust does fail properly here but hopefully,
someone knows of a nice way to handle this.
Thanks
--Phil
On Mon, 11 Apr 2022 at 11:35, Philip Herron wrote:
>
> 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 our CI doesn't pick this up as a failure and
> so I have pushed a patch directly to master to disable the offending
> test case. I am raising this here just for transparency for why I
> pushed to master and I hope the build farm is ok it might be worth
> cancelling any existing builds and letting them pick up the next
> merge's to master. For reference I pushed this patch to silence the
> issue: 68458036c81d141a3899ac4e6ec6ddf0fdfde174
>
> Hope everyone is having a great start of the week.
>
> --Phil
--
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust
☠ Buildbot (Wildebeest Builder): gccrust - failed 'grep unexpected ...' (failure) (master)
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 Worker: fedora-ppc64le Build Reason: (unknown) Blamelist: liushuyu Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/4/logs/stdio - warnings (31): https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/4/logs/warnings__31_ - 5: make check ( warnings ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/5/logs/stdio - rust.sum: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/5/logs/rust_sum - rust.log: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/5/logs/rust_log - warnings (3): https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/5/logs/warnings__3_ - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/60/builds/1729/steps/6/logs/stdio -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
☠ Buildbot (Wildebeest Builder): gccrust - failed 'grep unexpected ...' (failure) (master)
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: debian-i386 Build Reason: (unknown) Blamelist: Philip Herron Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/3/logs/stdio - 4: make ( warnings ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/4/logs/stdio - warnings (130): https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/4/logs/warnings__130_ - 5: make check ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/5/logs/stdio - rust.sum: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/5/logs/rust_sum - rust.log: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/5/logs/rust_log - 6: grep unexpected rust.sum ( failure ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/62/builds/1440/steps/6/logs/stdio -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
☠ Buildbot (Wildebeest Builder): gccrust - failed compile (failure) (master)
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-arm64 Build Reason: (unknown) Blamelist: Arthur Cohen , bors[bot] <26634292+bors[bot]@users.noreply.github.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/1/logs/stdio - 2: rm -rf gccrs-build ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/3/logs/stdio - 4: make ( failure ) Logs: - stdio: https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/4/logs/stdio - warnings (58): https://builder.wildebeest.org/buildbot/#builders/58/builds/1807/steps/4/logs/warnings__58_ -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
