<< I think it could be very useful if integrated with CI. We could find many issues that aren't detected currently. >>
Thanks Alan, that's a great idea! Lemme find the best way to integrate Automated Testing into the CI, without breaking our PR Submissions. If a PR breaks the CI: Maybe we can run an "Auto Triage" to guess the Severity of the Breakage? Like: (1) Code Red: "Most likely the PR Code broke the CI, please fix the PR" (2) Code Amber: "Maybe the PR Code broke the CI? Needs more investigation" (3) Code Green: "Probably OK" (e.g. unable to download OpenAMP, automated test failed) Right now I'm running the Automated Test every morning (GMT+8). So I have the rest of the day to figure out what broke, without staying up all night :-) Lup On Sun, Jan 28, 2024 at 7:36 AM Alan C. Assis <acas...@gmail.com> wrote: > Hi Lup, > > Congratulations, I think it could be very useful if integrated with CI. > > We could find many issues that aren't detected currently. > > Best Regards, > > Alan > > On Sat, Jan 27, 2024 at 8:05 PM Lee, Lup Yuen <lu...@appkaki.com> wrote: > > > Every day we’re auto-building NuttX for Ox64 BL808 RISC-V SBC... Can we > > test NuttX on Ox64 automatically after building? > > > > Yes we can! With a little help from the Ox64 BL808 Emulator that we > created > > last week. In this article, we fill in the missing pieces of our Ox64 > > Emulator and run it for Automated Testing... > > > > (1) Booting NuttX in Supervisor Mode (instead of Machine Mode) > > (2) Emulate OpenSBI for setting the System Timer > > (3) Emulate the UART Interrupts for Console Input > > (4) Execute everything with Expect Scripting (based on TCL) > > (5) Which becomes our Daily Automated Testing (triggered every day by > > GitHub Actions) > > > > Here's the article: https://lupyuen.codeberg.page/articles/tinyemu3.html > > > > Lup > > >
