Recordsgolanggithub.com/go-logr/logrv1.4.1github.com/go-logr/logr/testr.NewWithInterface
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- github.com/go-logr/logr v1.4.1: testr.NewWithInterface 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. HOWgithub.com/go-logr/logr/testr.NewWithInterface MIT-0 · 2026-08-27
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 1✕ · PROJECT_PROCESS 5✓ — Verified: UNKNOWN 0✓ 1✕
|
ELEVATED FAILURE | 6 | 1 | 71% | 1 | 2026-08-30 |
| go 1.26 · Go · go · linux musl · docker
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-27 |
snapshot · 2026-08-31
Failure clusters
-
observed PROJECT_TEST Evidence gap ×20 v1.4.1 → v1.4.2 → v1.4.4 runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-17 · Last seen: 2026-08-20Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×8 v1.4.1 → v1.4.3 os=linux · runtime=go@1.26 sha256:964ddac6b19a…<path> <str> imported and not usedgo/compiler · compiler-diagnostic · outer go run, go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31
-
observed PROJECT_COMPILE exit 1 ×3 v1.4.1 → v1.4.3 os=linux · runtime=go@1.26 github.com/go-logr/logr/testr.NewWithInterface sha256:d5fae02e8604…test/contract.go:<n>:<n>: <str> imported and not usedgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-31
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.4.1 os=linux · runtime=go@1.26 github.com/go-logr/logr/testr.NewWithInterface sha256:b3cefa76e1a2…FAIL: contextual log format unexpected: worker: <str>=0 <str>=<str> <str>=<str> <str>=<str> · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v1.4.1 os=linux · runtime=go@1.26 sha256:5902e1adcc93…test/contract_test.go:<n>:<n>: <str> imported and not used · test/contract_test.go:<n>:<n>: declared and not used: capturedPrefixgo/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31