gotestyourself / gotestyourself/gotestsum
passed reruns do not cache correctly?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
This is kind of surprising behavior, unless you know details about how Go does test caching.
When using gotestsum --rerun-fails, if the first run fails but the package ultimately passes, that result doesn't really get cached.
This is because go test doesn't treat -run specially. It doesn't cache the result at a function level at all. I did more investigation and a repro here: https://github.com/nfi-hashicorp/gotestsum-rerun-caching
I'm not sure there's anything to be done about this?
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 with the linked gotestsum-rerun-caching reproduction and the --rerun-fails flow. Compare the first failing run and subsequent package run under Go's test cache; done means establishing whether gotestsum can alter this behavior or documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100