Some weird difference between bisectable and committable
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<AlexDaniel> c:
8bed4a67b^,8bed4a67b run(:err, :out, :env(%(MVM_SPESH_NODELAY=>1, MVM_SPESH_BLOCKING=>1)), (run :out, ‘which’, ‘perl6-gdb-m’).out.slurp-rest.chomp, ‘sandbox/roast/S02-types/num.t’).out.slurp-rest.contains(‘SIGSEGV’).say
<committable6> AlexDaniel, ¦8bed4a67b^: «False» ¦8bed4a6: «True»
But at the same time:
<AlexDaniel> bisect:
old=8bed4a67b^ new=8bed4a67b run(:err, :out, :env(%(MVM_SPESH_NODELAY=>1, MVM_SPESH_BLOCKING=>1)), (run :out, ‘which’, ‘perl6-gdb-m’).out.slurp-rest.chomp, ‘sandbox/roast/S02-types/num.t’).out.slurp-rest.contains(‘SIGSEGV’).say
<bisectable6> AlexDaniel, On both starting points (old=8bed4a67b^ new=8bed4a6) the exit code is 0 and the output is identical as well
<bisectable6> AlexDaniel, Output on both points: «False»
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 by reproducing the committable and bisectable commands shown in the issue for commits 8bed4a67b^ and 8bed4a67b. Compare their exit codes and output, then identify and fix the cause of the disagreement so both bots report consistent results.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100