Discard the result if the thing times out
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: 2017.01,HEAD for ^13000 { $ = $_ for "/home/bisectable/.bash_history".IO.lines };
<benchable6> AlexDaniel, starting to benchmark the 2 given commits
<benchable6> AlexDaniel, ¦«2017.01»:10.0012¦«HEAD»:10.0009
<AlexDaniel> o_o
Results clearly show the time limit, which is a bit useless…
I think it should stop immediately if the first commit times out. If something in the middle timed out, then it should simply discard it.
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
No files or tests are named. Trace the benchmark timeout handling for the two-commit example, then verify that a timed-out first commit stops the run and a timed-out middle commit is omitted from the results.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100