Recordsgolanggolang.org/x/timefailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestSometimesEvery (0.00s) · rate_test.go:<n>: expected count 3, got 4 · FAIL test_time 0.128s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:c20f6be3a975…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.11.0 → first failing release v0.15.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/time v0.15.0: rate.NewLimiter This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWrate.NewLimiter MIT-0 · 2026-09-01
- golang.org/x/time v0.15.0: rate.Limiter This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWrate.Limiter MIT-0 · 2026-09-01
- golang.org/x/time v0.15.0: rate.Every This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWrate.Every MIT-0 · 2026-09-01