aboutsummaryrefslogtreecommitdiff
path: root/src/net/http/httputil/reverseproxy.go
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2025-11-20 16:21:09 -0500
committerGopher Robot <gobot@golang.org>2025-11-20 15:01:20 -0800
commitd58b733646d2d52638b08d5c44afbc7292aeca4d (patch)
tree661dfaf3d3b6252bf4892c42c2d9b4e7eb17a951 /src/net/http/httputil/reverseproxy.go
parent1bc54868d4fd03e3716e7ad9669d87c34c8aaa2d (diff)
downloadgo-d58b733646d2d52638b08d5c44afbc7292aeca4d.tar.xz
runtime: track goroutine location until actual STW
TestTraceSTW / TestTraceGCSTW currently tracks the location (M/P) of the target goroutines until it reaches the "start" log message, assuming the actual STW comes immediately afterwards. On 386 with TestTraceGCSTW, it actually tends to take >10ms after the start log before the STW actually occurs. This is enough time for sysmon to preempt the target goroutines and migration them to another location. Fix this by continuing tracking all the way until the STW itself occurs. We still keep the start log message so we can ignore any STW (if any) before we expect. Cq-Include-Trybots: luci.golang.try:gotip-linux-386-longtest,gotip-linux-amd64-longtest Change-Id: I6a6a636cf2dcb18d8b33ac4ad88333cabff2eabb Reviewed-on: https://go-review.googlesource.com/c/go/+/722520 Reviewed-by: Michael Knyszek <mknyszek@google.com> Auto-Submit: Michael Pratt <mpratt@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Diffstat (limited to 'src/net/http/httputil/reverseproxy.go')
0 files changed, 0 insertions, 0 deletions