From: Vineet Gupta <vineetg@rivosinc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, kevinl@rivosinc.com
Cc: Jeff Law <jlaw@ventanamicro.com>,
gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@gmail.com>,
jiawei@iscas.ac.cn, christoph.muellner@vrull.eu
Subject: Re: RISC-V Test Errors and Failures
Date: Tue, 16 May 2023 19:08:48 -0700 [thread overview]
Message-ID: <fb3fcbb3-520a-791a-9a99-cc15674e2b5d@rivosinc.com> (raw)
In-Reply-To: <mhng-1a62b138-235e-4b5b-9c78-e21bb70c5356@palmer-ri-x1c9a>
On 5/16/23 18:29, Palmer Dabbelt wrote:
> On Tue, 16 May 2023 18:04:37 PDT (-0700), Vineet Gupta wrote:
>> + Christoph, Jiawei
>>
>> On 5/16/23 17:20, Palmer Dabbelt wrote:
>>>> We really need to add some CI around RV toolchains to trip on these
>>>> sooner !
>>>
>>> Sounds like you're volunteering to set one up?
>>
>> Patrick's github CI patch seems to be a great start. Lets wait for it to
>> get merged, that will at least catch rv toolchain snafus: although the
>> granularity of testing is not ideal (tc changes are not so frequent)
>
> You mean riscv-gnu-toolchain changes? That's not super useful for GCC
> development, they're on a fork.
Well they are still useful to catch various snafus in toolchain plumbing
itself - I've run into 2 of those and Patcrick 2 himself, when trying to
use latest upstream toolchain scripts. But sure they are not testing
bleeding edge gcc.
>
>> I think the most pressing need is bleeding edge gcc regression tracking.
>> @Jeff is anything setup on sourceware and/or usable ? I thought they
>> do have existing bots for some arches to spin up build / run - perhaps
>> runs are native and not qemu.
>
> IIRC Jeff said his builders were hanging right now.
Jeff it seems has his own test infra. I was asking if sourceware (or
whatever the custodian of gcc project has).
I'd be really surprised if primary arches such as x86/aarch64 don't have
any test bots there ?
>
>> FWIW rivos gitlab CI (not public) has capability to track upstream gcc
>> (Kevin almost has it working), but there is no easy way to publish it
>> for rest of the world and I'd rather that be done in a public infra.
>
> +Kevin
>
> At least having the failure lists public would be a must-have, and I
> think that's tricky to do with gitlab.
Yep.
> Bjorn and Conor have something glued to the kernel patchwork that
> uploads test results to github as snippits, but IIRC we're trying to
> replace it with something more directly visible.
>
>> Didn't ISCAS/PLCT have such infra - sorry Kito asked the same question
>> this morning, but I was not fully awoke so don't remember what Jiawei
>> replied.
>
> I didn't even remember he asked ;)
next prev parent reply other threads:[~2023-05-17 2:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 23:06 Palmer Dabbelt
2023-05-17 0:16 ` Vineet Gupta
2023-05-17 0:20 ` Palmer Dabbelt
2023-05-17 1:04 ` Vineet Gupta
2023-05-17 1:29 ` Palmer Dabbelt
2023-05-17 2:00 ` Jeff Law
2023-05-17 2:05 ` Palmer Dabbelt
2023-05-17 2:32 ` Jeff Law
2023-05-17 2:39 ` Palmer Dabbelt
2023-05-17 4:08 ` Jeff Law
2023-05-17 2:08 ` Vineet Gupta [this message]
2023-05-17 2:12 ` Jeff Law
2023-05-17 7:52 ` Andreas Schwab
2023-05-19 0:13 ` Vineet Gupta
2023-05-25 20:29 ` Thomas Schwinge
2023-05-26 0:04 ` Vineet Gupta
2023-05-17 1:57 juzhe.zhong
2023-05-17 2:02 ` Andrew Pinski
2023-05-17 2:07 juzhe.zhong
2023-05-17 2:13 ` Palmer Dabbelt
2023-05-17 2:20 ` Kito Cheng
2023-05-17 2:21 ` Kito Cheng
2023-05-17 2:46 ` Vineet Gupta
2023-05-17 2:47 ` Palmer Dabbelt
2023-05-17 2:51 ` Patrick O'Neill
2023-05-17 2:53 ` Palmer Dabbelt
2023-05-17 3:08 ` Vineet Gupta
2023-05-17 3:11 ` Palmer Dabbelt
2023-05-17 3:33 ` Kito Cheng
2023-05-17 4:04 ` Jeff Law
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=fb3fcbb3-520a-791a-9a99-cc15674e2b5d@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=jlaw@ventanamicro.com \
--cc=kevinl@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).