git bisect for performance tests

Open
#7,688 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
git, r
Domain
performance

Research direction

Start by reviewing the manual procedure described in issue 7687's linked comment and locating the repository's existing performance-test entry point. Establish how a bisect run should select revisions and compare results; done means a repeatable workflow can identify the change that altered a performance result without relying on GitHub pull sorting.

Written by the indexing model from the issue text.

Description

atime

it would be nice if there was an easy way to run git bisect to find when a performance test result changed, as I did manually here
https://github.com/Rdatatable/data.table/issues/7687#issuecomment-4162931822
it was difficult using the Github pulls page because there is no sort by merge date https://github.com/orgs/community/discussions/136568

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.