Mirror of forum.nim-lang.org

10325 :: Bisect bugs GitHub Action

• juancarlospaco (orginal) [2023-07-06T17:34:22+02:00] view original

  GitHub Actions bot to Git bisect bugs from GitHub issue comments code blocks.

  The bot will run the provided code on all Nim final versions from 1.0.0 to devel, then finds at least 1 commit that fails and finds at least 1 commit that works, bisects commit-by-commit between that range of commits (FAILS..WORKS), re-builds Nim commit-by-commit and runs the code checking if it works, until it finds 1 specific commit that introduces the Bug, it says who, when, why, link, and files with the bug.

  Also reports debug info like output, IR (C/JS), AST (macro bug), date/time/duration, compiled file size, commits near with link (for context), commits per second (bisect speed), etc.

  The reduced bug repro code sample should be as tiny and simple as possible for faster performance but must have asserts.

  • Users can bisect their own bugs, core devs get the commit that introduced the bug.
  • More debug tooling without adding more code to any Nim repos.
  • Does not add more time to main CI runs, its only for new issue comments.

  Real world use in Nim repo: https://github.com/nim-lang/Nim/issues/16933#issuecomment-1620907872

  https://github.com/juancarlospaco/nimrun-action#nimrun-action

---

• termer (orginal) [2023-07-10T06:06:05+02:00] view original

  This is amazing. I'd like to re-create this on some of my projects because it would save such a headache.

---