From: Jeff Law <jlaw@ventanamicro.com>
To: Vineet Gupta <vineetg@rivosinc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
kevinl@rivosinc.com
Cc: 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 20:12:08 -0600 [thread overview]
Message-ID: <a648eed6-b5a7-aee9-3b0d-5eb59983aa28@ventanamicro.com> (raw)
In-Reply-To: <fb3fcbb3-520a-791a-9a99-cc15674e2b5d@rivosinc.com>
On 5/16/23 20:08, Vineet Gupta wrote:
>>
>>> 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 ask
Mine is the closest we've got for project-wide testing. Various orgs
have their own servers/bots.
jeff
next prev parent reply other threads:[~2023-05-17 2:12 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
2023-05-17 2:12 ` Jeff Law [this message]
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=a648eed6-b5a7-aee9-3b0d-5eb59983aa28@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kevinl@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=vineetg@rivosinc.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).