Automatically detect wrong bisection results due to flapping code
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there's this check:
https://github.com/Raku/whateverable/blob/cf9bcd03b154bcc570aca8a2628099a408cde460/xbin/Bisectable.p6#L266-L268
However, @lizmat++ and @Altai-man++ came up with an idea of doing this check automatically by comparing .moarvm files of the final commit and its parent.
I have a suspicion that rakudo in the past did not produce the same .moarvm file reproducibly, meaning that the check won't work on old commits. However, we can still do some checks, for example we can check if all changed files in the commit were to doc files.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in xbin/Bisectable.p6 around lines 266-268, where the existing wrong-bisection check is performed. Investigate how to compare the final commit's .moarvm file with its parent and how to identify changed documentation files; done means flapping results are detected automatically without relying on the manual check.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100