gopls/internal/test/integration: faster execution time Running the gopls integration tests was bottlenecked by running all tests in dual modes (Default and Forwarded), serial test queuing, and redundant LSP server sessions. This change applies several optimizations to the integration tests: 1. regtest.DefaultModes: Return Default mode by default in non-short runs, doing rfindley's TODO. Running every test in both Default and Forwarded mode duplicated LSP server boots and disk sandboxes. Dedicated smoke tests (TestSimultaneousEdits, TestForwardedSmoke, and TestDebugServer) in the misc package maintain explicit coverage for Forwarded mode. 2. Parallelization: Added t.Parallel() to 20 isolated test functions in misc/rename_test.go and 61 top-level test functions in diagnostics/diagnostics_test.go. Because each test executes in its own isolated sandbox (t.TempDir()) and uses an in-process pipe server, they safely run concurrently. 3. didcreatefiles_test.go: Removed duplicate subtest 12 (an exact duplicate of subtest 11) and consolidated the remaining 11 subtests into a single shared LSP session. Measurements (Mac / Linux): - Full (go test ./... ./gopls/...): - Mac: ~450s -> 387s (~63s saved) - Linux: ~210s -> ~140s (~70s saved) - Short (go test -short ./... ./gopls/...): - Warm cache: 192s -> 91s (Mac) / ~45s -> ~35s (Linux) - Cold clean: ~5.5-6.5m -> ~3m40s-4m01s (Mac) / ~90s -> ~72s (Linux) - Single packages short mode (Mac / Linux): - misc: 95s / 28s -> 69s / 22s - diagnostics: 35s / 15s -> 18s / 9s - workspace: 43s / 12s -> 32s / 10s Change-Id: Ic42a523a69f4a3ef36b23104e2a279deda51e6fa Reviewed-on: https://go-review.googlesource.com/c/tools/+/833125 Reviewed-by: Alan Donovan <adonovan@google.com> LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This repository provides the golang.org/x/tools module, comprising various tools and packages mostly for static analysis of Go programs, some of which are listed below. Use the “Go reference” link above for more information about any package.
It also contains the golang.org/x/tools/gopls module, whose root package is a language-server protocol (LSP) server for Go. An LSP server analyses the source code of a project and responds to requests from a wide range of editors such as VSCode and Vim, allowing them to support IDE-like functionality.
Selected commands:
cmd/goimports formats a Go program like go fmt and additionally inserts import statements for any packages required by the file after it is edited.cmd/callgraph prints the call graph of a Go program.cmd/digraph is a utility for manipulating directed graphs in textual notation.cmd/stringer generates declarations (including a String method) for “enum” types.cmd/toolstash is a utility to simplify working with multiple versions of the Go toolchain.These commands may be fetched with a command such as
go install golang.org/x/tools/cmd/goimports@latest
Selected packages:
go/ssa provides a static single-assignment form (SSA) intermediate representation (IR) for Go programs, similar to a typical compiler, for use by analysis tools.
go/packages provides a simple interface for loading, parsing, and type checking a complete Go program from source code.
go/analysis provides a framework for modular static analysis of Go programs.
go/callgraph provides call graphs of Go programs using a variety of algorithms with different trade-offs.
go/ast/inspector provides an optimized means of traversing a Go parse tree for use in analysis tools.
go/cfg provides a simple control-flow graph (CFG) for a Go function.
go/gcexportdata and go/gccgoexportdata read and write the binary files containing type information used by the standard and gccgo compilers.
go/types/objectpath provides a stable naming scheme for named entities (“objects”) in the go/types API.
Numerous other packages provide more esoteric functionality.
This repository uses Gerrit for code changes. To learn how to submit changes, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/tools.
The main issue tracker for the tools repository is located at https://go.dev/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.
This repository uses prettier to format JS and CSS files.
The version of prettier used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.