From: Philip Herron <philip.herron@embecosm.com>
To: gcc-rust@gcc.gnu.org
Subject: Bad testcase
Date: Mon, 11 Apr 2022 11:35:22 +0100 [thread overview]
Message-ID: <CAB2u+n1oDDLjkYZ_CaSWPd251OqzAX=0y=5U+WP5Uw4EYj_Npg@mail.gmail.com> (raw)
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
next reply other threads:[~2022-04-11 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:35 Philip Herron [this message]
2022-04-11 10:39 ` Philip Herron
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB2u+n1oDDLjkYZ_CaSWPd251OqzAX=0y=5U+WP5Uw4EYj_Npg@mail.gmail.com' \
--to=philip.herron@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).