lupyuen/lupyuen.org
1
0
Fork 0
mirror of https://github.com/lupyuen/lupyuen.github.io.git synced 2025-01-13 06:48:34 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update article

Browse source
This commit is contained in:
Lup Yuen Lee 2024-12-17 19:03:05 +08:00
parent 7cc3dacaeb
commit 69de1a1c2a
6 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
images/ci7-dashboard2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 577 KiB

BIN
images/ci7-title2.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 98 KiB

BIN
images/ci7-title3.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 132 KiB

BIN
images/ci7-title4.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 149 KiB

BIN
images/ci7-title5.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 150 KiB

16
src/ci7.md
View file

@ -24,6 +24,8 @@ The Bug Stops Here! In this article, we study the internals of the __NuttX CI Te
- TODO
![TODO](https://lupyuen.github.io/images/ci7-title2.jpg)
# Run the CI Test
__Thanks to Docker:__ We can run __CI Test _risc-v-05___ on our Ubuntu PC. And figure out why it fails _rv-virt:citest_...
@ -73,6 +75,8 @@ Which is totally unhelpful. Why is it failing?
[(See the __Complete Log__)](https://gist.github.com/lupyuen/c59a642a3f3c5934ec53d5d72dd6e01d)
![TODO](https://lupyuen.github.io/images/ci7-title3.jpg)
# Snoop the CI Test
To understand what went wrong: We connect to the __Docker Container__. And snoop the __Background Processes__...
@ -126,6 +130,8 @@ Let's inspect the Log File...
[(See the __Complete Log__)](https://gist.github.com/lupyuen/399d2ba7d964ba88cdbeb97f64778a0e)
![TODO](https://lupyuen.github.io/images/ci7-title4.jpg)
# Dump the CI Log File
From above: We see that everything goes into this __CI Test Log File__...
@ -162,6 +168,8 @@ Hmmm this looks super interesting...
That's why CI Test hangs, refuses to accept NSH Test Commands, and fails all subsequent tests!
![TODO](https://lupyuen.github.io/images/ci7-title5.jpg)
# Test NuttX on QEMU RISC-V
_What if we test rv-virt:citest on QEMU?_
@ -223,6 +231,8 @@ We'll probably [__Rewind The Build__](https://lupyuen.github.io/articles/ci6#wha
[(But __another bug__ appears. Exactly like Kafka on Groundhog Day!)](https://github.com/apache/nuttx/issues/15170)
![Continuous Integration Test for Apache NuttX RTOS (QEMU RISC-V)](https://lupyuen.github.io/images/ci7-title.jpg)
# Why So Difficult?
1. _What's this Pytest we saw earlier?_
@ -269,10 +279,16 @@ We'll probably [__Rewind The Build__](https://lupyuen.github.io/articles/ci6#wha
Someday we could call Pytest to do [__Test-Driven Development__](https://en.wikipedia.org/wiki/Test-driven_development) of NuttX Apps and NuttX Drivers. Which means we can write the Test Cases in Pytest, before writing a Single Line of NuttX Code!
![No more CI Test errors yay!](https://lupyuen.github.io/images/ci7-dashboard2.png)
[_No more CI Test errors yay!_](https://nuttx-dashboard.org)
# What's Next
Next Article: We'll chat about an __Experimental Mastodon Server__ for NuttX Continuous Integration.
Maybe Later: Let's chat about __Git Bisect__ and how we discover Breaking Commits in NuttX.
Many Thanks to the awesome __NuttX Admins__ and __NuttX Devs__! And my [__GitHub Sponsors__](https://github.com/sponsors/lupyuen), for sticking with me all these years.
- [__Sponsor me a coffee__](https://github.com/sponsors/lupyuen)