Recordsgolanggithub.com/rogpeppe/go-internalv1.9.0
Change the conditions
Current conditions
github.com/rogpeppe/go-internal @v1.9.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-06
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.9.0
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:f33789b8002b74022f79f090f8bbfaa5480553e339bb2428a13305fc502fb6d0
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/pkg/diff | v0.0.0-20210226163009-20ebb0f2a09e | UNKNOWN No linked outcome measured | nothing measured | 4 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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 | v1.9.0 | v1.3.0 |
|---|---|---|
| github.com/pkg/diff | v0.0.0-20210226163009-20ebb0f2a09e | — |
| gopkg.in/errgo.v2 | — | v2.1.0 |
Moved: 0 · unchanged at every release: 2
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.
Recent failure clusters
-
observed PROJECT_TEST exit 1 ×1 v1.9.0 os=linux · runtime=go@1.26 sha256:f33789b8002b…--- FAIL: TestCCheck (0.00s) · === RUN TestCDeferAndDone · contract_test.go:<n>: expected 2 deferred functions to run on Done(), got 0 …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06
-
observed PROJECT_COMPILE exit 1 ×1 v1.9.0 os=linux · runtime=go@1.26 sha256:17537f9fa97a…test/contract.go:<n>:<n>: <str> imported and not used · test/contract.go:<n>:<n>: <str> imported and not used …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06
-
observed UNKNOWN exit 2 Evidence gap ×1 v1.9.0 os=linux · runtime=go@1.26 sha256:00e630595b1e…flag provided but not defined: -e · usage: go run [build flags] [-exec xprog] package [arguments...] · Run <str> for details.go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.9.0 os=linux · runtime=go@1.26 sha256:c3b94b545859…panic: testing: Verbose called before Parse · goroutine 1 [running]: · testing.Verbose(...) · <path>:<n>go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate