public inbox for
 help / color / mirror / Atom feed
From: Philip Herron <>
Subject: Re: Bad testcase
Date: Mon, 11 Apr 2022 11:39:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.



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:
> 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

      reply	other threads:[~2022-04-11 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 10:35 Philip Herron
2022-04-11 10:39 ` Philip Herron [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).