Go: Fixing Vet's Failure Handling in Multi-Package Tests
A single commit from Alan Donovan fixes a bug where "go test" across multiple packages could cascade into unrelated build failures when one package failed vet checks. The fix ensures downstream packages can still find type and fact data in memory, even when an upstream vet run exits with errors.
Duration: PT2M5S
Episode overview
This episode is a short developer briefing from Go.
It explains recent repository work in plain language.
- Show: Go
- Published: 2026-09-06T13:05:46Z
- Audio duration: PT2M5S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, it's September 6th, and this is Go.
Today's focus is a single but consequential fix in the go command's build and test pipeline, addressing a subtle failure mode that turns one package's vet complaint into a wave of unrelated test failures.
Here's the core issue. When you run "go test" across multiple packages, the toolchain runs vet in the background without JSON output. If vet finds diagnostics in one package, it exits non-zero. That's expected and intentional — vet actions are built to ignore that failure so downstream packages still get vetted and…
Commit 38d1265 closes that gap. If the vet tool exits non-zero but still successfully writes its output file, the builder now records that result in memory so dependent actions in the same build graph can still find the necessary types and facts. Importantly, the fix preserves cache correctness: the vetx file is…
What's next: this is tracked against issue 81188, suggesting there's more cleanup coming as unitchecker's transition to self-contained vetx exports continues. Expect more edge cases surfacing as that migration proceeds.
That's the briefing for today. Thanks for listening to Go.
Nearby episodes from Go
- Weekly Recap - Security Hardening and Runtime Memory Discipline
- Certificate Parsing Gets Stricter, TLS Memory Gets Leaner
- Plugin Bug Fix and Protocol Correctness
- SVE Expands, Compiler Correctness Cleanup
- Compiler Analysis Gets Sharper, Runtime Gets Less Blocking
- Compiler Efficiency and HTTP Cleanup
- Aliasing Bugs and Correctness Cleanup in Math Big
- Weekly Recap - Correctness Fixes Across the Stack