No description
  • Go 95.2%
  • Assembly 4.4%
  • C 0.2%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Alan Donovan 38d1265e1a cmd/go: preserve vet export data in memory for dependent actions on failure
When "go test" is applied to multiple packages, it runs cmd/vet
without -json (in contrast to "go vet"). If a package has diagnostics,
the vet tool prints them to stderr and exits nonzero.

Vet actions in the build graph set IgnoreFail so that upstream
diagnostics do not suppress vetting and testing of downstream
packages. However, when sh.run returns an error, Builder.vet returns
immediately without recording a.built.

Previously this was benign because unitchecker imported types from the
compiler's export data (cfg.PackageFile), treating missing .vetx
entries in cfg.PackageVetx as merely lacking analyzer facts. However,
with unitchecker transitioning to doing its own type export through
.vetx files, a missing .vetx file causes downstream typechecking to
fail entirely ("no package vetx file for ..."), causing downstream
test runs to fail with "[build failed]".

This change ensures that if the vet tool exited non-zero but nonetheless
successfully produced its output file (vcfg.VetxOutput), a.built is still
recorded in memory so that downstream actions in the same build graph
can locate the dependency's types and facts.

To preserve cache integrity:
- The .vetx file is only written to the persistent cache (cache.Default)
  when runErr == nil.
- runErr is still returned, ensuring that the failing package is still
  reported as a failure and its own test binary is not run.

Updates #81188

Change-Id: I26d36c0d1874dc1f78162cc84b6eeebe513b643d
Reviewed-on: https://go-review.googlesource.com/c/go/+/827884
LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Michael Matloob <matloob@google.com>
Auto-Submit: Alan Donovan <adonovan@google.com>
Reviewed-by: Michael Matloob <matloob@golang.org>
2026-09-05 15:11:17 -07:00
.github .github: update PULL_REQUEST_TEMPLATE to match the latest instruction 2026-05-26 15:10:06 -07:00
api net/http: add MethodQuery constant 2026-08-26 20:57:21 -07:00
doc net/http: make Transport.CancelRequest into a no-op 2026-08-31 12:45:48 -07:00
lib lib/time: update to 2026c/2026c 2026-07-09 11:24:04 -07:00
misc all: replace strings.Split with strings.SplitSeq 2025-09-15 17:34:45 -07:00
src cmd/go: preserve vet export data in memory for dependent actions on failure 2026-09-05 15:11:17 -07:00
test cmd/compile: correctly mark interface calls as used for tail call wrappers 2026-09-04 15:09:50 -07:00
.gitattributes all: treat all files as binary, but check in .bat with CRLF 2020-06-08 15:31:43 +00:00
.gitignore .gitignore: ignore go test artifacts 2025-11-10 12:41:03 -08:00
codereview.cfg codereview.cfg: add codereview.cfg for master branch 2021-02-19 18:44:53 +00:00
CONTRIBUTING.md doc: normalize proposal-process links 2023-03-29 22:00:27 +00:00
go.env cmd/go: additional doc-inspired tests and bug fixes 2023-06-06 19:18:46 +00:00
LICENSE LICENSE: update per Google Legal 2024-08-09 14:54:31 +00:00
PATENTS
README.md README: fix CC BY license name 2024-07-22 17:45:27 +00:00
SECURITY.md SECURITY.md: update the Reporting a Vulnerability link 2023-09-22 21:17:24 +00:00

The Go Programming Language

Go is an open source programming language that makes it easy to build simple, reliable, and efficient software.

Gopher image Gopher image by Renee French, licensed under Creative Commons 4.0 Attribution license.

Our canonical Git repository is located at https://go.googlesource.com/go. There is a mirror of the repository at https://github.com/golang/go.

Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.

Download and Install

Binary Distributions

Official binary distributions are available at https://go.dev/dl/.

After downloading a binary release, visit https://go.dev/doc/install for installation instructions.

Install From Source

If a binary distribution is not available for your combination of operating system and architecture, visit https://go.dev/doc/install/source for source installation instructions.

Contributing

Go is the work of thousands of contributors. We appreciate your help!

To contribute, please read the contribution guidelines at https://go.dev/doc/contribute.

Note that the Go project uses the issue tracker for bug reports and proposals only. See https://go.dev/wiki/Questions for a list of places to ask questions about the Go language.