Recordsgolanggithub.com/go-logr/logrfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestWithInsecureContract (10.00s) · contract_test.go:<n>: expected at least one gRPC trace export request, got none …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:b6b84f5f81cf…
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.
- v1.4.4 PASS 64 passing observations
- v1.4.3 PASS 213 passing observations
- v1.4.2 FAIL
- v1.4.1 PASS 13 passing observations
- v1.3.0 PASS 3 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02
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 v1.4.1 → first failing release v1.4.2
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v1.4.2 → first passing release v1.4.3
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
- github.com/go-logr/logr v1.4.2 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. HOW MIT-0 · 2026-08-24
- github.com/go-logr/logr v1.4.2 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. HOW MIT-0 · 2026-08-19