mirror of https://github.com/golang/go.git
There are two possible quick fixes for a missing go.sum entry, and the regression tests always run all available fixes. That never made sense, but I never got around to fixing it because it didn't cause a problem. Now that it turns out to be the cause of the problem described in CL 315152, fix it and roll that CL back. Change-Id: I49430429a99a412f43bd11b30afe8903db99a694 Reviewed-on: https://go-review.googlesource.com/c/tools/+/315910 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> |
||
|---|---|---|
| .. | ||
| analysisinternal | ||
| apidiff | ||
| event | ||
| fakenet | ||
| fastwalk | ||
| gocommand | ||
| gopathwalk | ||
| imports | ||
| jsonrpc2 | ||
| jsonrpc2_v2 | ||
| lsp | ||
| memoize | ||
| packagesinternal | ||
| proxydir | ||
| span | ||
| stack | ||
| testenv | ||
| tool | ||
| typesinternal | ||
| xcontext | ||