Recordsgolangmodernc.org/memoryv1.11.0
Change the conditions
Current conditions
modernc.org/memory @v1.11.0windows 11 · x64 · go 1.26 · go
package-level total, not an API
1 of 1 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
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 3 ·
Steady 0
First observed break
v1.11.0
windows · go@1.26
269 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/sys | v0.46.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| modernc.org/mathutil | v1.7.1 | CANDIDATE Correlated change; unproven combination | contract passed | 17 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.12.0 | v1.11.0 | v1.5.0 |
|---|---|---|---|
| golang.org/x/sys | v0.47.0 | v0.46.0 | — |
| modernc.org/mathutil | v1.7.1 | v1.7.1 | v1.5.0 |
Moved: 2 · unchanged at every release: 0
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 ESM Evidence gap ×269 v1.11.0 os=windows · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-16 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_COMPILE Evidence gap ×7 v1.11.0 os=windows · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-18 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×6 v1.11.0 sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-27 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 Evidence gap ×3 v1.11.0 runtime=go@1.26 sha256:c2ae6d87252c…go/compiler · build-aggregate · outer go test · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-27 · Last seen: 2026-09-15Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ×2 v1.11.0 os=windows · runtime=go@1.26 sha256:2d0e4470127c…--- FAIL: TestOperationsRequiresVerifiedFleetBeforeServerRestart (0.00s) …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26
-
observed UNKNOWN Evidence gap ×2 v1.11.0 os=windows · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-27 · Last seen: 2026-08-27Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERROR ×2 v1.11.0 os=windows · runtime=go@1.26 sha256:b7219112d875…--- FAIL: TestTheRemoteRunnerIsFailClosed (0.63s) …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-09
-
observed PROJECT_TEST exit 1 ERROR ×2 v1.11.0 os=windows · runtime=go@1.26 sha256:e7ea28870f3d…--- FAIL: TestTheRemoteRunnerIsFailClosed (0.70s) …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-09 · Last seen: 2026-09-15
-
observed UNKNOWN exit 1 Evidence gap ×2 v1.11.0 os=windows · runtime=go@1.26 sha256:30c7aeb70296…Traceback (most recent call last): · File <str>, line 120, in <module> · main() · File <str>, line 42, in mainpython · unclassified-diagnostic · outer python · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERROR ×2 v1.11.0 os=windows · runtime=go@1.26 sha256:1e6b1e2fdeb5…--- FAIL: TestTheRemoteRunnerIsFailClosed (0.71s) …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_PROCESS exit 1 ×1 v1.11.0 os=windows · runtime=go@1.26 sha256:727bc9226330…production deploy gate: unsafe migration: migration 0026_anomaly_reports.sql contains a statement outside the automatic additive allowlist: CREATE TABLE …Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26
-
observed PROJECT_PROCESS exit 1 ×1 v1.11.0 os=windows · runtime=go@1.26 sha256:a0ca5eae5863…production deploy gate: target <token> is not in canonical origin/main · exit status 1Evidence quality: complete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26
Showing the 12 most-reported of 251 recorded failure clusters. The rest are single reports.