Recordsgolanggithub.com/google/pprofv0.0.0-20210407192527-94a9f03dee38github.com/google/pprof/profile.Merge
Change the conditions
Current conditions
github.com/google/pprof/profile.Merge @v0.0.0-20210407192527-94a9f03dee38ubuntu glibc · x64 · go 1.26 · go 1
3 of 3 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-04
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.0-20210407192527-94a9f03dee38
linux · go@1.26
1 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:e5345872019a415adea1ad2c772122fe839fbc36b92ea599fa27e3b0280a4c83
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/chzyer/readline | v0.0.0-20180603132655-2972be24d48e | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/ianlancetaylor/demangle | v0.0.0-20200824232613-28f6c0f3b639 | CANDIDATE Correlated change; unproven combination | 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 | v0.0.0-20231212022811-ec68065c825e | v0.0.0-20210407192527-94a9f03dee38 | v0.0.0-20200708004538-1a94d8640e99 | v0.0.0-20200229191704-1ebb73c60ed3 |
|---|---|---|---|---|
| github.com/chzyer/readline | v1.5.1 | v0.0.0-20180603132655-2972be24d48e | v0.0.0-20180603132655-2972be24d48e | v0.0.0-20180603132655-2972be24d48e |
| github.com/ianlancetaylor/demangle | v0.0.0-20230524184225-eabc099b10ab | v0.0.0-20200824232613-28f6c0f3b639 | v0.0.0-20181102032728-5e5cf60278f6 | v0.0.0-20181102032728-5e5cf60278f6 |
| github.com/chromedp/chromedp | v0.9.2 | — | — | — |
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.
Recent failure clusters
-
observed PROJECT_RESOLVE exit 1 ×1 v0.0.0-20210407192527-94a9f03dee38 os=linux · runtime=go@1.26 sha256:e5345872019a…test/contract.go:<n>:<n>: missing go.sum entry for module providing package github.com/google/pprof/profile (imported by sample/test); to add:go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04