Flakiness monitoring
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
We should monitor build/test flakiness in CI (particularly innerloop) to detect new issues in jobs that perform retries and to make it easier to justify closing old issues.
- May share some details with other monitoring: https://github.com/microsoft/go/issues/2154
- Would help close out issues like https://github.com/microsoft/go/issues/1611
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.
Research direction
Start by reviewing the related monitoring issue 2154 and the flakiness issue 1611. Define how CI, particularly innerloop jobs that perform retries, should expose new flakiness and provide evidence for closing old issues; the work is done when that monitoring approach is specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, observability, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100