Re: RISC-V Test Errors and Failures

[Palmer Dabbelt <palmer@dabbelt.com>]

On Tue, 16 May 2023 19:32:21 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 5/16/23 20:05, Palmer Dabbelt wrote:
>> On Tue, 16 May 2023 19:00:12 PDT (-0700), Jeff Law wrote:
>>>
>>>
>>> On 5/16/23 19:29, Palmer Dabbelt 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.
>>> Correct.  More precisely, the riscv64 builds hang.  Not sure if it's
>>> stage2 or stage3 of the bootstrap.  Been happening for the last couple
>>> weeks.  I suspect some codegen bug in the riscv port.  I'll have to
>>> bisect it which will be quite painful.
>>
>> Can anyone else do it?  If the only blocker for having an upstream
>> regression CI thing is just sorting out why it broke over the last few
>> weeks then I'm happy to try and trick someone around here into doing
>> some work...
> Probably easiest for me unless someone else has a chroot environment
> handy.  It's not hard to do the bisection, it just involves a lot of
> waiting.

By "chroot environment" you mean something like a 
debootstrap-into-chroot with qemu-user/binfmt-misc?  I don't have that 
setup right now, but it wouldn't be a big lift.

> I've just about got the my problem from earlier today under control,
> then I can probably start bisection.

That's fine with me, I have plenty of other stuff to do ;)