"calls tick repeatedly" test is flaky.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
go test ./...
ok github.com/dogmatiq/testkit 1.023s
Running Suite: github.com/dogmatiq/testkit/engine_test
======================================================
Random Seed: 1606293184
Will run 18 of 18 specs
••••••••••••••
------------------------------
• Failure [0.017 seconds]
func Run()
/Users/james/grit/github.com/dogmatiq/testkit/engine/run_test.go:16
calls tick repeatedly [It]
/Users/james/grit/github.com/dogmatiq/testkit/engine/run_test.go:34
Expected
<int>: 4
to be >=
<int>: 6
/Users/james/grit/github.com/dogmatiq/testkit/engine/run_test.go:52
------------------------------
•••
Summarizing 1 Failure:
[Fail] func Run() [It] calls tick repeatedly
/Users/james/grit/github.com/dogmatiq/testkit/engine/run_test.go:52
Ran 18 of 18 Specs in 0.078 seconds
FAIL! -- 17 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestSuite (0.08s)
This happens occasionally on CI.
Contributor guide
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 engine/run_test.go, especially the “calls tick repeatedly” test around lines 34 and 52, and run go test ./... to reproduce the intermittent failure. Investigate why the test sometimes observes fewer ticks on CI; done means the test passes reliably without losing coverage of repeated ticking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100