Something fishy with pre-2015.09 commits
Open
Nobody has claimed this yet.
help wanted
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
See this query: https://gist.github.com/Whateverable/040c7ae7b6aec814d2d5d5098ec5d115
96 builds are skipped because “Commit exists, but a perl6 executable could not be built for it”. I don't think that this is true. There's some other issue with them (or bisectable prints the wrong reason).
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 with the linked Whateverable query and inspect the 96 skipped pre-2015.09 builds. Trace whether the reported reason, “Commit exists, but a perl6 executable could not be built for it,” matches the actual failure or whether bisectable is reporting the wrong cause. Done means identifying and correcting the reason shown for these commits.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100