Build seL4 and seL4test for all supported platforms

seL4 / ci-actions

CI GitHub actions for the seL4 repositories

https://sel4.systems

3 stars 13 forks source link

Build seL4 and seL4test for all supported platforms #282

Open Ivan-Velickovic opened 1 year ago

Ivan-Velickovic commented 1 year ago

I believe the current status of the CI (for sel4test at least) is that not all platforms that claim to be supported are tested. Obviously we cannot buy all the hardware to actually run the tests, but just compiling them to eliminate any build errors is trivial.

Here's what I've seen missing so far:

[x] QEMU RISC-V virt 32-bit (here)
[x] Polarfire (https://github.com/seL4/ci-actions/pull/328)
[ ] Rocketchip
[ ] Rocketchip based on ZCU102 FPGA
[ ] Ariane
[ ] Ultra96v2
[ ] TK1-SOM (not sure what this is, the docs page is missing instructions for building sel4test)
[x] Raspberry Pi 3B (32 bit only)
[x] Raspberry Pi 4B (64 bit only)
[ ] Raspberry Pi 4B (32 bit, #288)

lsf37 commented 1 year ago

Agreed. At least compiling does definitely male sense, yes.

lsf37 commented 1 year ago

This should be relatively easy to achieve and should only need the corresponding entries in the platforms.yml file.

lsf37 commented 8 months ago

Actually, RPI3 and RPI4 are in the test and have been built regularly for quite a while. Have you checked the build logs for the rest of the list? (or the platforms.yml file -- disabled means no hardware test, but still build. Only no_hw_build excludes a platform from the build).

Ivan-Velickovic commented 8 months ago

Can you point me to a run where they were built? I can't see it as part of the CI that runs for the kernel itself, e.g https://github.com/seL4/seL4/actions/runs/7380751924/job/20078457216.

Ivan-Velickovic commented 8 months ago

Nevermind, my browser did not load the log file properly. I can see RPi3 being built for 32-bit and RPi4 being built for 64-bit. I think when I created the issue I meant to say that since we have both of those platforms we should also do run-time tests, but that can be a separate issue.

Basically just wanted a list of everything that either needs to be tested at run-time as well if we have the hardware, or only build-time if we don't.