Hi Yanfeng and Alan: I have been running Daily OSTest for NuttX QEMU RISC-V, hosted on GitHub Actions:
(1) OSTest for 32-bit QEMU RISC-V runs OK on GitHub Actions: 32-bit Flat Build (rv-virt:nsh): https://github.com/lupyuen/nuttx-riscv64/actions/workflows/qemu-riscv-nsh.yml 32-bit Kernel Build (rv-virt:knsh32): https://github.com/lupyuen/nuttx-riscv64/actions/workflows/qemu-riscv-knsh32.yml (2) But OSTest for 64-bit QEMU RISC-V fails on GitHub Actions (wonder why): 64-bit Flat Build (rv-virt:nsh64) crashes with: "fpu_test: Started task FPU#1 / riscv_exception: Illegal instruction" https://github.com/lupyuen/nuttx-riscv64/blob/main/.github/workflows/qemu-riscv-nsh64.yml#L2 64-bit Kernel Build (rv-virt:knsh64) hangs at: "ostest_main: Started user_main" https://github.com/lupyuen/nuttx-riscv64/blob/main/.github/workflows/qemu-riscv-knsh64.yml#L2 (3) That's why I run a script on my Home Computer to download the 64-bit Daily Builds and run OSTest locally: 64-bit Flat Build (rv-virt:nsh64): https://github.com/lupyuen/nuttx-riscv64/releases/tag/qemu-riscv-nsh64-2024-08-08 64-bit Kernel Build (rv-virt:knsh64): https://github.com/lupyuen/nuttx-riscv64/releases/tag/qemu-riscv-knsh64-2024-08-08 So we might still need a Local Computer to run some of the QEMU RISC-V tests. Lup On Thu, Aug 8, 2024 at 11:10 AM yfliu2008 <yfliu2...@qq.com.invalid> wrote: > Alan, > > > Just want to add that besides a testing farm, we can also leverage the > cheap QEMU more in our CI. > > > For example, the "rv-virt" target now supports most configurations that > are used on other riscv devices, so it can be a good representative for > riscv devices in general. On the other hand, almost all recent failures on > k230 devices can be reproduced on QEMU, if we had "ostest" based smoke > testing coverage in our CI, those fake k230 issues can be prevented earlier. > > > > Regards, > Yanfeng > > > > > Original > > > > From:"Alan C. Assis"< acas...@gmail.com >; > > Date:2024/7/19 3:14 > > To:"dev"< dev@nuttx.apache.org >; > > Subject:Help us to create a distributed board testing farm > > > Hi Everyone, > > We are creating a testing farm for NuttX to be integrated on our CI. > > As you know, NuttX supports more than 300 boards and we need to test all > boards everytime someone modifies our code base. > > So, let's to map each person have each board, please include your name in > the front of each board you have (case there is already some else name > there, put your name in the next column) > > > https://docs.google.com/spreadsheets/d/1nDMquG-gjfQ0c9jIfv_HztGeq1ysfCeJzOEts3X3Eks/edit?gid=0#gid=0 > > Thank you very much! > > BR, > > Alan
