Recordsgolanggithub.com/prometheus/procfsfailure issue
Failure signature
UNKNOWN signal KILLED Evidence gap ×1
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.46.0 · go: downloading go.opentelemetry.io/otel/log v0.22.0 …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-08 · Last seen: 2026-09-08
sha256:6658a586a256…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-08 → 2026-09-08
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.22.0 | v0.21.1 | v0.20.1 |
|---|---|---|---|
| golang.org/x/sync | v0.22.0 | v0.22.0 | v0.20.0 |
| golang.org/x/sys | v0.47.0 | v0.48.0 | v0.45.0 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 |
Moved: 2 · unchanged at every release: 1
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.