Recordsgolanggithub.com/go-logr/logrfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: assignment mismatch: 1 variable but otlptrace.New returns 2 values …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:e84876b56a4e…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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 10 passing observations
- v1.4.3 PASS 23 passing observations
- v1.4.2 FAIL
- v1.4.1 not measured
- v1.3.0 not measured
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 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
- Releases in this window never measured at PROJECT_COMPILE: 2
- 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