[libre-riscv-dev] sorry state of ieee754fpu repo -- CI desperately needed

Luke Kenneth Casson Leighton lkcl at lkcl.net
Sat Apr 11 17:10:57 BST 2020


On Sat, Apr 11, 2020 at 4:56 PM Frieder Paape <frieder at paape.io> wrote:
>
> Hi,
>
> finally I found some time to look into this, I've seen that Jacob
> already wrote the CI test and its working fine. My next steps would be
> to mark all tests that are currently failing as skipped. And then fix
> them one by one.
>
> I am however a bit confused about my tasks because Luke says I should
> give priority to the CI logging, which I believe Jacob has already taken
> care of in rust. I do know the language so I could help out there as well.

great.  the sooner we can free jacob up to help with the hardware
design on the memory subsystem the better (this is rapidly becoming a
critical path task, jacob)

> Finally I have access to Jacobs build server now. I'd like to ask again
> what my tasks here are. I can see if I can reconfigure gitlab-runner to
> limit it's disk space. Also I understood that I should try and install
> gitlab on the server?

yes please - sufficient to run ci.

l.



More information about the libre-riscv-dev mailing list