firecracker-microvm / firecracker-microvm/firecracker-containerd
Can we auto-track the flakiness of our tests?
Open
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Description
Something like https://github.blog/2020-12-16-reducing-flaky-builds-by-18x/?
Contributor guide
Research direction
The issue does not name any files, tests, or CI entry points. Start by reading the linked GitHub article and reviewing this repository’s test and CI configuration to identify where test results and reruns are recorded. Done would require an agreed design and an implemented way to track and report test flakiness.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100