Recordsgolanggithub.com/Azure/azure-pipeline-gofailure issue
Failure signature
PROJECT_RESOLVE exit 2 ×1
github.com/mattn/go-ieproxy@v0.0.0-20190610004146-91bb50d98149: missing go.sum entry for go.mod file; to add it:
Evidence quality: complete · go/module · resolve-diagnostic · outer go · First recorded: 2026-10-23 · Last seen: 2026-10-23
sha256:2b5706b57a17…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.2.1 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-23 → 2026-10-23
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/Azure/azure-pipeline-go v0.2.1 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. HOW MIT-0 · 2026-10-23