[Feedback] PR Test Bot

[lupyuen]

Please provide your feedback for the PR Test Bot, that will Build a Test a PR on Real Hardware. Here are commands for PR Test Bot:

## For Avaota-A1 Arm64 SBC (Allwinner A537)
@nuttxpr test avaota-a1:nsh

## For Milk-V Duo S 64-bit RISC-V SBC (Sophgo SG2000)
@nuttxpr test milkv_duos:nsh

## For QEMU Arm64 (Flat Build) and RISC-V 64-bit (Kernel Build)
@nuttxpr test qemu-armv8a:netnsh
@nuttxpr test rv-virt:knsh64

These commands will trigger an Email Alert to me. Please give me 12 Hours to review the PR (making sure there isn't malicious code) before I start the PR Test Bot. The results shall be posted as a PR Comment.

How does it work? Check out the articles:

• "Test Bot for Pull Requests ... Tested on Real Hardware (Apache NuttX RTOS / Oz64 SG2000 RISC-V SBC)"

• "QEMU Test Bot for Pull Requests: Beware of Semihosting Breakout (Apache NuttX RTOS)"

• "Porting Apache NuttX RTOS to Avaota-A1 SBC (Allwinner A527 SoC)"

[tmedicci]

@lupyuen , I have a question:

If I understood correctly, anyone could trigger (by tagging @nuttxpr) the testbot but I'd only run if you "like" the message that tagged it? Is that correct?

[lupyuen]

@tmedicci Right now I have to review manually every Test Bot request, for security issues. Please tag me @lupyuen after sending a @nuttxpr request :-)

[lupyuen]

how can I add my milkv_duos to the CI? It should be nice if we could run this test automatically without calling the nuttxpr bot manually

Hmmm are we thinking of triggering the Hardware Test directly from CI? There's a problem: The PR might contain malicious scripts or code, that could mess up our Test PC and Network. We should review the PR Code before doing the Hardware Test.

We could do this instead (and it already works today)

1. Anyone may post a PR comment: @nuttxpr test milkv_duos:nsh or @nuttxpr test avaota-a1:nsh
2. Right now, this will trigger an Email Alert to me
3. I will review the PR for malicious code
4. Then I will start the PR Test Bot manually
5. Please gimme some time to review the PR, in case I'm sick (or out for marathon training)

Or if we prefer to run the Hardware Test Manually, without calling any GitHub API:

git clone https://github.com/lupyuen/nuttx-build-farm
cd nuttx-build-farm

## For Milk-V Duo S and Oz64 SG2000:
## Build and Test github.com/Fix-Point/nuttx, branch timer-improve
./build-test.sh oz64 \
  /tmp/build-test.log \
  HEAD HEAD \
  https://github.com/Fix-Point/nuttx timer-improve \
  https://github.com/apache/nuttx-apps master

## For Avaota-A1: Change oz64 to avaota
## Needs a MicroSD Multiplexer

This requires:

1. A TFTP Server to be installed for hosting the NuttX Image
2. On Milk-V Duo S: U-Boot should be configured to boot NuttX over TFTP