Recordsgolanggolang.org/x/textfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestOTLPMetricHTTPExporterContract (0.00s) · === RUN TestWithTemporalitySelectorOption · --- PASS: TestWithTemporalitySelectorOption (0.00s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:68a7069b7aae…
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.
- v0.24.0 PASS 4 passing observations
- v0.23.0 PASS 20 passing observations
- v0.22.0 PASS 6 passing observations
- v0.21.0 FAIL
- v0.20.0 PASS 1 passing observations
- v0.18.0 PASS 3 passing observations
- v0.17.0 PASS 2 passing observations
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.20.0 → first failing release v0.21.0
What differs across the boundary
- golang.org/x/tools v0.47.0 → v0.21.1-0.20240508182429-e35e4ccd0d2d hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.21.0 → first passing release v0.22.0
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v0.24.0 | v0.23.0 | v0.22.0 | v0.21.0 | v0.20.0 | v0.18.0 | v0.17.0 |
|---|---|---|---|---|---|---|---|
| golang.org/x/tools | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.31.0 | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.47.0 | — | v0.21.1-0.20240508182429-e35e4ccd0d2d |
Moved: 1 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.