public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Jim Wilson <jim.wilson.gcc@gmail.com>
Cc: Nelson Chu <nelson.chu@sifive.com>, gcc-regression@gcc.gnu.org
Subject: Re: [TCWG CI] Regression caused by binutils: RISC-V: Added ld testcases for the medlow and medany code models.
Date: Tue, 21 Dec 2021 17:36:23 +0300 [thread overview]
Message-ID: <CE907640-5944-420A-A61F-B9CC9031C872@linaro.org> (raw)
In-Reply-To: <6f6e31bc-7a49-bc70-acd8-f5d403c81a73@gmail.com>
> On 19 Dec 2021, at 01:45, Jim Wilson via Gcc-regression <gcc-regression@gcc.gnu.org> wrote:
>
> On 12/18/21 01:16, ci_notify--- via Gcc-regression wrote:
>> [TCWG CI] Regression caused by binutils: RISC-V: Added ld testcases for the medlow and medany code models.:
>> commit fdb2b35b8fdbd5a6c136db326c73582dbfb335f8
>> Author: Nelson Chu <nelson.chu@sifive.com>
>> RISC-V: Added ld testcases for the medlow and medany code models.
>
> This doesn't make any sense. How does adding a RISC-V specific linker testcase break ARM builds? Even worse, I can find no useful info in the logs about what actually broke. It appears that your testing scripts are broken. Please disable your regression testing until you fix your scripts. Or at least modify them so that they don't bother innocent people with false and misleading bug reports.
Hi Jim,
This was sent out due to a bug in our CI. Sorry for the noise.
This particular problem was caused by a scripts patch merged on Friday, and it had whole weekend to run wild. This is a lesson to us to not “improve” CI at the end of the week.
Regards,
--
Maxim Kuvyrkov
https://www.linaro.org
parent reply other threads:[~2021-12-21 14:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6f6e31bc-7a49-bc70-acd8-f5d403c81a73@gmail.com>]
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=CE907640-5944-420A-A61F-B9CC9031C872@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=nelson.chu@sifive.com \
/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).