Re Run if Base of PR has changed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- ci-cd, performance
Research direction
Start by locating the performance comparison workflow and the check that finds no results when the PR base SHA changes. Trace how a changed base is handled, then verify that this condition triggers a new base run and produces results available for comparison.
Written by the indexing model from the issue text.
Description
It can happen, that when a perf comparison is finally run, the base SHA of the PR has changed and therefore no results are available to compare.
This should trigger a re-run of the base
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from AutoPas/PerformanceTesting
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Timeline Plot Axis Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in AutoPas/PerformanceTesting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100