Benchable may test the same commit more than once
Open
Nobody has claimed this yet.
benchable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<AlexDaniel> benchable6: 1615c83^,1615c83 my int $foo; for ^200_000 { when NaN { $foo = $foo + 1 }; when 1e0 { $foo = $foo - 100 } }
<benchable6> AlexDaniel, starting to benchmark the 2 given commits
<benchable6> AlexDaniel, benchmarked the given commits, now zooming in on performance differences
<benchable6> AlexDaniel, ¦1615c83^: «0.9356» ¦f16cf37: «0.9511» ¦1615c83: «1.2309»
1615c83^ and f16cf37 is actually the same commit.
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 benchable6 example with 1615c83^ and 1615c83, then trace how the command resolves and schedules the requested commits. Done means equivalent commit references are recognized as one commit and are benchmarked only once.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100