You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test: fix three flaky tests that the release check and CI found #217
The first run of the Release check (#199) and the CI runs of #215 and #216 on 2026-11-18 failed on tests in code that these changes did not touch. A re-run passed each time, so the tests are flaky. The stress check of the Release check (-race -count=5 -cpu 1,2,4) will fail on them before each release.
test/contract: contract: the trial broker did not stop cleanly: exit status 1 (Go stable, twice on ci: verify the draft release's files before publishing #216). It may be two packages that use the fixed trial directory nodkey-try at the same time.
Also: golangci-lint on main at 9d63080 reported nolintlint ("directive ... is unused for linter gosec") for the G703 directives in internal/store/home.go and internal/store/helpers_test.go; the next run passed. The gosec G703 result seems not stable.
Done when
Each of the three tests passes go test -race -count=20 -cpu 1,2,4 on its package, or the cause is fixed in the code.
For 1: it is written down whether a value could stay in memory, and if so, the fix and a test for it.
The lint note on internal/store is stable (it passes or fails the same way every run).
Activity