Idea: Fixing test flakiness
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
I have a theory that the reason why we see some test flakiness is because we are running tests in parallel on already starved GitHub actions VMs. This issue is about testing that theory and removing flakiness.
Some ideas:
- Try not running tests in parallel. `go test -p ./...` instead.
- This will significantly slow down our test times. We could offset this by caching test results and only testing things that have changed.
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 examining the GitHub Actions test setup and running the proposed `go test -p ./...` experiment. Compare whether reducing parallelism affects the reported flakiness, then evaluate test-result caching as a way to offset slower runs. Done means the cause is supported or rejected and a concrete path to reliable tests is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100