tree 8f95b09582cf1c977e49fe99b8853d095accfc81
parent 8b7669898d7c1172aa248c0626ff2e5a3f33ced7
author Rebecca Stambler <rstambler@golang.org> 1592284634 -0400
committer Rebecca Stambler <rstambler@golang.org> 1592589655 +0000

internal/gocommand: use semaphores to ensure correct serialization

Piped go commands cannot run concurrently, as a user may be looking at
the stdout/stderr, and we don't want to show any load concurrency
errors. We use a semaphore with a maximum number of in-flight go
commands to make sure that all running go commands have completed before
starting a piped command.

Change-Id: Ie027d9ff704fb7dd9640da06569345e89ed7a012
Reviewed-on: https://go-review.googlesource.com/c/tools/+/238059
Run-TryBot: Rebecca Stambler <rstambler@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Cottrell <iancottrell@google.com>
Reviewed-by: Heschi Kreinick <heschi@google.com>