kernelci / kernelci/kernelci-pipeline
Regression tracker must retry test 1-2 times before registering regression
Open
techdebt
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
Before registering regression in "[regression_tracker.py](https://github.com/kernelci/kernelci-pipeline/blob/main/src/regression_tracker.py)" - send retry to test, to make sure it is not flaky test of test lab glitch.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/regression_tracker.py and trace where a regression is registered after a test result. Review the surrounding flow to determine how a test can be retried one or two times before registration. Done means transient failures or lab glitches receive the requested retries before a regression is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100