kernelci / kernelci/kernelci-pipeline
Revisit timed-out node submission to KCIDB
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
As per the discussion, I have disabled timed-out checkout, build, job, and test nodes to KCIDB as it doesn't contain any useful information (just error code and no logs to debug further) atm.
@nuclearcat is already working on job retry logic and we will wait for incomplete nodes to finish before sending them to KCIDB.
Revisit the disabling logic added in https://github.com/kernelci/kernelci-pipeline/pull/920 once the job retry is in place.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the disabling logic added in pull request #920, then examine the job retry logic and how incomplete nodes are handled before KCIDB submission. Done means timed-out checkout, build, job, and test nodes are revisited consistently once retries are in place, with incomplete nodes sent after they finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100