Finding the Breaking Commit in Apache #NuttX RTOS ... Let's automate with Git Bisect
Here's how we automate Git Bisect in Apache #NuttX RTOS
Article: https://lupyuen.org/articles/bisect.html#automated-bisect
Git Bisect in Apache #NuttX RTOS ... Here's how it works
Article: https://lupyuen.org/articles/bisect.html#simulate-the-git-bisect
Git Bisect works great for fixing #NuttX Builds ... Fixing CI Test? Not so great
Article: https://lupyuen.org/articles/bisect.html#continuous-integration-test
Git Bisect works best for bugs that are Reliably Reproducible ... It probably won't work for #NuttX CI Test
Article: https://lupyuen.org/articles/bisect.html#good-commit-goes-bad
Fixing 2 bugs in #NuttX CI Test ... By increasing the Stack Size
Article: https://lupyuen.org/articles/bisect.html#fixing-the-bug
How we increase the Stack Size for #NuttX CI Test
Article: https://lupyuen.org/articles/bisect.html#increase-the-stack
Inspecting the Size of a #NuttX Executable with Bloaty
Article: https://lupyuen.org/articles/bisect.html#appendix-inspect-executable-size-with-bloaty
Finding the Breaking Commit in Apache #NuttX RTOS ... Let's automate with Git Bisect
https://lupyuen.org/articles/bisect.html
Suppose we hit a Runtime Bug in Apache NuttX RTOS. We think that the Breaking Commit (causing the bug) is somewhere inside these hundreds of NuttX Commits. But which one? In this article: We run Git Bisect to discover the Breaking Commit.
lupyuen.org