Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for SIM/QEMU automation script #14007

Closed
wants to merge 1 commit into from
Closed

Conversation

GUIDINGLI
Copy link
Contributor

Summary

Hi all,

Here open a new PR just for :
Requesting SIM/QEMU automation script

Especially the compile cmd, run cmd.

Recently we push lots of PR to the community, but some of them have regression, like:
#13651

So can someone/anyone share your automation script to us.
Then we can integrate it to CI, and catch the regression.

Impact

None

Testing

None

@masayuki2009
@fdcavalcanti
@lupyuen

@github-actions github-actions bot added Area: Tooling Area: CI Size: XS The size of the change in this PR is very small labels Oct 9, 2024
@lupyuen
Copy link
Member

lupyuen commented Oct 9, 2024

@GUIDINGLI That's a great idea! I run these scripts daily at GitHub Actions:

GitHub Actions won't run OSTest correctly for 64-bit QEMU. I run these scripts on my computer instead:

  • test-nsh64.sh: Automated Testing of Apache NuttX RTOS for QEMU RISC-V 64-bit Flat Build
  • test-knsh64.sh: Automated Testing of Apache NuttX RTOS for QEMU RISC-V 64-bit Kernel Build

I'm not sure why GitHub Actions is failing for 64-bit QEMU. Here's what I discovered:

@lupyuen
Copy link
Member

lupyuen commented Oct 10, 2024

Here's another option: We can run the Milk-V Duo S Emulator in GitHub Actions: https://lupyuen.github.io/articles/sg2000b

This morning we caught a Serial Driver problem during the Daily Auto-Test:
https://github.com/lupyuen/nuttx-sg2000/actions/runs/11265744154/job/31329258960

spawn ./temu nuttx.cfg
TinyEMU Emulator for Sophgo SG2000 SoC
A�BC

Normally it runs like this:
https://github.com/lupyuen/nuttx-sg2000/actions/runs/11246511514/job/31268441936

spawn ./temu nuttx.cfg
TinyEMU Emulator for Sophgo SG2000 SoC
A�BC
NuttShell (NSH) NuttX-12.7.0-RC0
nsh> uname -a
NuttX 12.7.0-RC0 6ce7b70a3a Oct  9 2024 00:15:20 risc-v milkv_duos

@GUIDINGLI
Copy link
Contributor Author

Here's another option: We can run the Milk-V Duo S Emulator in GitHub Actions: https://lupyuen.github.io/articles/sg2000b

This morning we caught a Serial Driver problem during the Daily Auto-Test: https://github.com/lupyuen/nuttx-sg2000/actions/runs/11265744154/job/31329258960

spawn ./temu nuttx.cfg
TinyEMU Emulator for Sophgo SG2000 SoC
A�BC

Normally it runs like this: https://github.com/lupyuen/nuttx-sg2000/actions/runs/11246511514/job/31268441936

spawn ./temu nuttx.cfg
TinyEMU Emulator for Sophgo SG2000 SoC
A�BC
NuttShell (NSH) NuttX-12.7.0-RC0
nsh> uname -a
NuttX 12.7.0-RC0 6ce7b70a3a Oct  9 2024 00:15:20 risc-v milkv_duos

Fix on :
#14033

@lupyuen
Copy link
Member

lupyuen commented Oct 13, 2024

This might be helpful when something breaks: This script will Auto-Test the Past 50 Commits on NuttX QEMU knsh64: https://github.com/lupyuen/nuttx-riscv64/blob/main/special-qemu-riscv-knsh64.sh#L42-L56

@GUIDINGLI
Copy link
Contributor Author

This might be helpful when something breaks: This script will Auto-Test the Past 50 Commits on NuttX QEMU knsh64: https://github.com/lupyuen/nuttx-riscv64/blob/main/special-qemu-riscv-knsh64.sh#L42-L56

Great, hope you can integrate them to our CI earlier.
I am not good at the CI, so may not be able to help you, Sorry.

@github-actions github-actions bot added Area: OS Components OS Components issues Size: S The size of the change in this PR is small and removed Area: Tooling Area: CI Size: XS The size of the change in this PR is very small labels Dec 11, 2024
@GUIDINGLI GUIDINGLI closed this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: OS Components OS Components issues Size: S The size of the change in this PR is small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants