Open matloob opened 4 years ago
cc @bcmills @jayconrod @ianthehat @mvdan
Change https://golang.org/cl/230378 mentions this issue: cmd/go: add a trace option to GODEBUG
Tracing like https://github.com/golang/go/issues/15736?
Yes, though my understanding is that --debug-actiongraph only has timing information for build actions, and doesn't cover cmd/go's behavior before actions are executed.
Change https://golang.org/cl/237683 mentions this issue: cmd/go: add a debug-trace flag to generate traces
Change https://golang.org/cl/237684 mentions this issue: cmd/go: add Context parameter to base.command.Run
Change https://golang.org/cl/238541 mentions this issue: cmd/go: propagate context into PackagesForBuild and Do for tracing
Change https://golang.org/cl/238542 mentions this issue: cmd/go/internal/trace: add function to distinguish Goroutines
Change https://golang.org/cl/238543 mentions this issue: cmd/go: add trace events for each action
Change https://golang.org/cl/239083 mentions this issue: cmd/go: mark trace flows between actions
Change https://golang.org/cl/239098 mentions this issue: cmd/trace: move viewer data structs into cmd/internal/traceviewer
Change https://golang.org/cl/239438 mentions this issue: cmd/go: process -debug-trace flag for cmd/test and cmd/vet
Change https://golang.org/cl/239437 mentions this issue: cmd/go: add tracing instrumentation to leod.TestPackagesFor
Change https://golang.org/cl/239750 mentions this issue: cmd/go: do context propagation for tracing downloads
Change https://golang.org/cl/239749 mentions this issue: cmd/go: add span for modload.LoadBuildList
Change https://golang.org/cl/240181 mentions this issue: cmd/go: do context propagation for tracing downloads
Change https://golang.org/cl/242365 mentions this issue: cmd/go: add trace spans for the skeleton of get
Change https://golang.org/cl/242785 mentions this issue: cmd/go: rewrite mvs.buildList to not use par.Work
Change https://golang.org/cl/242786 mentions this issue: cmd/go: add tracing for querying and downloading from the proxy
Change https://golang.org/cl/243949 mentions this issue: cmd/go: annotate ImportPathsQuiet and modload.(*loader).doPkg
Change https://golang.org/cl/243948 mentions this issue: cmd/go: add tracing to mvs.buildList
Change https://golang.org/cl/248322 mentions this issue: cmd/go: mark trace flows between actions
Change https://golang.org/cl/248328 mentions this issue: cmd/go: rewrite mvs.buildList to not use par.Work
Change https://golang.org/cl/248327 mentions this issue: cmd/go: do context propagation for tracing downloads
Change https://golang.org/cl/248324 mentions this issue: cmd/go: process -debug-trace flag for cmd/test and cmd/vet
Change https://golang.org/cl/248319 mentions this issue: cmd/go/internal/trace: add function to distinguish goroutines
Change https://golang.org/cl/248323 mentions this issue: cmd/go: add tracing instrumentation to load.TestPackagesFor
Change https://golang.org/cl/248325 mentions this issue: cmd/go: add span for modload.LoadBuildList
Change https://golang.org/cl/248320 mentions this issue: cmd/go: add trace events for each action
Change https://golang.org/cl/249017 mentions this issue: cmd/go: revert 3 CLs affecting par.Work, context propagation, tracing
Change https://golang.org/cl/249021 mentions this issue: cmd/go: do context propagation for tracing downloads
Change https://golang.org/cl/249022 mentions this issue: cmd/go: add tracing for querying and downloading from the proxy
Change https://go.dev/cl/419554 mentions this issue: cmd/go: add Context parameter to download function
Change https://go.dev/cl/452456 mentions this issue: cmd/go: propagate Context arguments through modfetch methods
I'd like to add a GODEBUG option to cmd/go to emit traces so that we can visualize build behavior. For now it will emit a runtime trace but maybe in the future we might use @ianthehat's events library. Maybe in the future it could become a flag, but for now adding it to GODEBUG should be safe in the sense that it doesn't affect the formal interface of the go command.