Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools/cmd/godoc: improve diagnostics for server hangs in TestWeb/GOPATH #50014

Closed
bcmills opened this issue Dec 7, 2021 · 18 comments
Closed
Assignees
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure. Tools This label describes issues relating to any tools in the x/tools repository.
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Dec 7, 2021

--- FAIL: TestWeb (37.91s)
    --- FAIL: TestWeb/GOPATH (15.11s)
        godoc_test.go:86: server failed to respond in 15s
FAIL
FAIL	golang.org/x/tools/cmd/godoc	68.450s

greplogs --dashboard -md -l -e 'FAIL: TestWeb .*\n\s+.*\n\s+.*server failed to respond'

2021-12-06T14:58:33-c882a49-f8a8a73/dragonfly-amd64
2021-12-05T12:50:44-c882a49-ecf6b52/dragonfly-amd64
2021-12-04T04:50:55-c882a49-549cfef/openbsd-386-70-n2d
2021-12-04T04:41:31-c882a49-cd5f2cf/dragonfly-amd64
2021-12-04T01:07:28-c882a49-fa88ba1/openbsd-386-70-n2d
2021-12-04T01:07:10-c882a49-ba83aa7/dragonfly-amd64
2021-12-03T22:57:02-c882a49-9ae0b35/openbsd-386-70-n2d
2021-12-03T21:25:05-c882a49-d20a0bf/dragonfly-amd64
2021-12-03T21:23:11-c882a49-b3e1fbf/dragonfly-amd64
2021-12-03T18:55:11-c882a49-0f2d0d0/openbsd-386-70-n2d
2021-12-03T18:55:02-f64c0f4-c4a8550/dragonfly-amd64
2021-12-03T18:27:20-e212aff-c4a8550/dragonfly-amd64
2021-12-03T01:09:21-e212aff-0985990/openbsd-386-70-n2d
2021-12-03T00:46:20-e212aff-8da66a3/dragonfly-amd64
2021-12-02T16:48:07-e212aff-36be0be/openbsd-386-70-n2d
2021-12-01T15:05:46-615f9a6-b7651e5/openbsd-386-70-n2d
2021-11-30T22:42:17-1fd30d2-7ccbcc9/openbsd-386-70-n2d
2021-11-30T18:09:02-2c9b078-931d80e/openbsd-386-70-n2d
2021-11-30T16:43:31-2c9b078-682435d/openbsd-386-70-n2d
2021-11-23T17:30:32-1e71a25-00045b7/openbsd-386-68
2021-11-16T01:10:28-4adea50-9e13a88/openbsd-386-68
2021-11-13T00:50:04-49ce184-c893a85/openbsd-386-68
2021-11-12T18:14:22-fda06c1-8b66b3d/openbsd-386-68
2021-11-10T22:16:25-fc3ed20-4d06839/openbsd-386-68
2021-11-09T20:10:50-e900012-5430203/openbsd-386-68
2021-11-09T18:23:16-e900012-55e6e82/openbsd-386-68
2021-11-02T20:49:06-6561d8c-b246873/openbsd-386-68
2021-08-06T19:38:52-d529aec-fa6aa87/dragonfly-amd64
2021-08-04T15:26:45-309db04-6e73886/dragonfly-amd64
2021-08-04T13:50:16-309db04-7921829/dragonfly-amd64
2021-08-03T19:59:22-32c652e-16ab7e4/dragonfly-amd64
2021-08-03T16:06:16-594b3a2-8a7ee4c/dragonfly-amd64
2021-08-03T16:06:16-594b3a2-7921829/dragonfly-amd64
2021-08-02T19:06:04-a668498-8a7ee4c/dragonfly-amd64
2021-07-27T22:01:54-07bc1bf-7cd10c1/dragonfly-amd64
2021-07-26T23:46:13-07bc1bf-840e583/dragonfly-amd64
2021-07-26T20:36:31-07bc1bf-ed8cbbc/dragonfly-amd64
2021-07-26T20:36:31-07bc1bf-ecaa681/dragonfly-amd64
2021-07-22T17:13:07-251092d-c6d89db/dragonfly-amd64
2021-07-21T23:55:41-412ee17-3e48c03/dragonfly-amd64
2021-07-21T20:52:30-7f68387-3e48c03/dragonfly-amd64
2021-07-21T16:31:48-7aa8294-bc51e93/dragonfly-amd64
2021-07-13T13:36:40-d36a54b-c6d89db/dragonfly-amd64
2021-07-12T16:16:36-980829d-ab4085c/dragonfly-amd64
2021-07-12T16:16:36-980829d-3d1d066/dragonfly-amd64
2021-07-10T00:32:22-5b540d3-ab4085c/dragonfly-amd64
2021-07-09T19:50:55-e33c0f2-ab4085c/dragonfly-amd64
2021-07-09T17:21:04-8e32e9f-fb052db/dragonfly-amd64
2021-07-08T23:16:08-6994825-3d1d066/dragonfly-amd64
2021-07-08T19:56:07-71eae3a-3d1d066/dragonfly-amd64
2021-07-07T20:25:29-fd00574-f264879/dragonfly-amd64
2021-07-02T16:25:10-7edcfe5-6125d0c/dragonfly-amd64
2021-07-01T01:38:42-f0847e0-9d65578/dragonfly-amd64
2021-06-30T22:02:09-f0847e0-4711bf3/dragonfly-amd64
2021-06-22T16:01:58-d25f906-5bd09e5/dragonfly-amd64

@bcmills bcmills added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Dec 7, 2021
@gopherbot gopherbot added the Tools This label describes issues relating to any tools in the x/tools repository. label Dec 7, 2021
@gopherbot gopherbot added this to the Unreleased milestone Dec 7, 2021
@bcmills
Copy link
Contributor Author

bcmills commented Dec 7, 2021

At this failure rate, this looks to me like a release-blocker via #11811. The test should either be fixed or skipped on the affected builders.

Looking at the test, I see at least three problems with the timeout strategy:

  1. If the server actually wedges, its output logs (and, critically, its goroutine dump) is not logged anywhere. (The process is killed with cmd.Process.Kill instead of a signal that would give it the opportunity to dump goroutines.)

  2. The deadlines are hard-coded, inconsistently, without comments explaining why those deadlines should be fundamental. (One server gets only 15s, while the others get two minutes each.)

Probably for this issue we can just fix (2), although it would be nice to address (1) as well.

@bcmills bcmills modified the milestones: Unreleased, Go1.18 Dec 7, 2021
@bcmills bcmills added okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 release-blocker labels Dec 7, 2021
@bcmills bcmills changed the title x/tools/cmd/godoc: frequent failures in TestWeb on dragonfly-amd64 builder x/tools/cmd/godoc: frequent failures in TestWeb/GOPATH on dragonfly-amd64 builder Dec 7, 2021
@bcmills
Copy link
Contributor Author

bcmills commented Dec 7, 2021

Looking at this further, the failures are always in TestWeb/GOPATH. Perhaps we should just skip that subtest in -short mode, since at this point most users are in module mode anyway.

@bcmills
Copy link
Contributor Author

bcmills commented Dec 10, 2021

TestWeb/GOPATH takes less than a second on my workstation. I think this is uncovering a real bug in either godoc or the test itself.`

@cherrymui cherrymui removed the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label Dec 14, 2021
@cherrymui
Copy link
Member

cc @dmitshur

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/373005 mentions this issue: internal/moreexec: add a utility package for manipulating os/exec.Cmd

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/377835 mentions this issue: internal/testenv: add a Command function that replaces exec.Command

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/377836 mentions this issue: cmd/godoc: streamline subprocesses

@bcmills bcmills self-assigned this Jan 12, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Jan 12, 2022

The test needs better diagnostics. Proposal #50436 is at the bottom of this yak stack, but in the meantime we can polyfill the needed API into an internal package.

@dmitshur dmitshur self-assigned this Jan 12, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Jan 21, 2022

Intriguingly, the dragonfly-amd64 failures are no longer occurring after the builder was upgraded for #50538 (thanks, @tuxillo!).

We should still add better failure diagnostics to this test, but since it is no longer failing on the builders it won't mask other regressions, and doesn't need to be a release-blocker.

@bcmills bcmills modified the milestones: Go1.18, Backlog Jan 21, 2022
@bcmills bcmills changed the title x/tools/cmd/godoc: frequent failures in TestWeb/GOPATH on dragonfly-amd64 builder x/tools/cmd/godoc: improve diagnostics for server hangs in TestWeb/GOPATH Feb 3, 2022
@bcmills bcmills added the NeedsFix The path to resolution is known, but the work has not been done. label Feb 3, 2022
@gopherbot gopherbot removed the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Feb 3, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Feb 24, 2022

Now seen on windows-arm64-11 too, so this appears to be completely platform-independent.

greplogs --dashboard -md -l -e 'FAIL: TestWeb .*\n\s+.*\n\s+.*server failed to respond' --since=2022-01-21

2022-02-17T17:38:22-411d040-eaf0405/windows-arm64-11

@bcmills bcmills removed this from the Backlog milestone Feb 24, 2022
@bcmills bcmills added this to the Go1.19 milestone Feb 24, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Mar 2, 2022

greplogs --dashboard -md -l -e 'FAIL: TestWeb .*\n\s+.*\n\s+.*server failed to respond' --since=2022-02-24

2022-03-02T11:33:18-ffa170d-fd2e1e7/dragonfly-amd64
2022-03-01T16:32:20-fb3622a-2199841/darwin-amd64-11_0

@bcmills
Copy link
Contributor Author

bcmills commented Mar 2, 2022

Marking as release-blocker for Go 1.19 due to the recent failure on the darwin-amd64-11_0 builder. (darwin/amd64 is a first class port.)

@bcmills
Copy link
Contributor Author

bcmills commented Apr 25, 2022

Lots of these on dragonfly-amd64 and windows-arm64-11, and a few on other ports too.

greplogs --dashboard -md -l -e 'FAIL: TestWeb .*\n\s+.*\n\s+.*server failed to respond' --since=2022-03-03

2022-04-22T22:35:03-fa7afc9-0bf545e/dragonfly-amd64
2022-04-22T20:11:24-fa7afc9-3e73241/dragonfly-amd64
2022-04-22T17:22:12-d567bc1-534a911/dragonfly-amd64
2022-04-22T15:44:57-5d7ca8a-1899472/dragonfly-amd64
2022-04-22T13:59:32-5d7ca8a-507b70d/dragonfly-amd64
2022-04-22T00:37:23-5d7ca8a-bf19163/dragonfly-amd64
2022-04-22T00:25:08-5d7ca8a-c9031a4/windows-arm64-11
2022-04-22T00:10:17-5d7ca8a-575fd88/dragonfly-amd64
2022-04-21T23:41:49-5d7ca8a-555bed9/dragonfly-amd64
2022-04-21T21:07:18-5d7ca8a-430ae97/windows-arm64-11
2022-04-21T21:06:36-5d7ca8a-4d96c3c/dragonfly-amd64
2022-04-21T17:46:26-5d7ca8a-a4bbcd4/windows-arm64-11
2022-04-21T17:37:05-5d7ca8a-b348389/dragonfly-amd64
2022-04-20T21:51:06-5d7ca8a-8b36445/dragonfly-amd64
2022-04-20T20:19:07-5d7ca8a-5834024/windows-arm64-11
2022-04-19T22:24:44-c02adcc-e858c14/windows-arm64-11
2022-04-19T17:08:06-5bb9c48-689dc17/windows-arm64-11
2022-04-18T22:14:50-00aa68c-c5edd5f/darwin-amd64-11_0
2022-04-17T00:58:13-46bc274-e948c33/dragonfly-amd64
2022-04-15T01:19:37-884ffcd-35a92f9/windows-arm64-11
2022-04-15T00:53:40-884ffcd-78bea70/windows-arm64-11
2022-04-07T18:45:34-48e6d8d-7139e8b/netbsd-arm64-bsiegert
2022-04-06T22:00:21-b3e0236-81ae993/darwin-amd64-11_0
2022-03-24T22:38:08-1e5ae83-a10a209/darwin-amd64-11_0
2022-03-24T22:24:35-78ff15e-88be85f/netbsd-arm64-bsiegert
2022-03-24T17:50:47-9fd677e-b95d332/darwin-arm64-11_0-toothrot
2022-03-20T21:02:35-5ea13d0-7eaad60/dragonfly-amd64
2022-03-20T16:05:03-5ea13d0-6673d5d/dragonfly-amd64
2022-03-20T15:54:23-5ea13d0-47efdcb/dragonfly-amd64
2022-03-20T03:01:15-5ea13d0-4d2da99/dragonfly-amd64
2022-03-18T23:20:51-5ea13d0-7ca6902/dragonfly-amd64
2022-03-18T23:20:41-5ea13d0-da9649e/dragonfly-amd64
2022-03-18T22:42:43-5ea13d0-cc2e7f3/dragonfly-amd64
2022-03-18T22:41:45-5ea13d0-e1fbf13/dragonfly-amd64
2022-03-18T22:14:14-5ea13d0-d68615f/dragonfly-amd64
2022-03-18T21:55:52-5ea13d0-58631ba/dragonfly-amd64
2022-03-18T21:52:11-5ea13d0-9a932c5/dragonfly-amd64
2022-03-18T21:26:31-5ea13d0-67f6b8c/dragonfly-amd64
2022-03-18T20:57:35-5ea13d0-9465878/dragonfly-amd64
2022-03-18T13:39:41-5ea13d0-4aa1efe/dragonfly-amd64
2022-03-18T12:07:27-779dfa4-12eca21/dragonfly-amd64
2022-03-17T21:30:21-779dfa4-79861be/dragonfly-amd64
2022-03-17T21:30:21-779dfa4-4aa1efe/dragonfly-amd64
2022-03-17T20:32:25-c7b0e9a-79861be/dragonfly-amd64
2022-03-17T15:18:29-c7b0e9a-88be85f/dragonfly-amd64
2022-03-17T15:18:29-c7b0e9a-4aa1efe/dragonfly-amd64
2022-03-17T13:53:41-e998cd2-4aa1efe/dragonfly-amd64
2022-03-17T13:53:34-877ec07-c379c3d/dragonfly-amd64
2022-03-17T13:53:34-877ec07-c379c3d/windows-arm64-11
2022-03-17T13:53:34-877ec07-88be85f/dragonfly-amd64
2022-03-17T08:43:51-85d68bc-c379c3d/dragonfly-amd64
2022-03-17T08:43:15-85d68bc-599d539/dragonfly-amd64
2022-03-17T01:29:17-85d68bc-6686536/dragonfly-amd64
2022-03-16T22:16:36-85d68bc-ed4db86/dragonfly-amd64
2022-03-16T22:16:36-85d68bc-88be85f/netbsd-arm64-bsiegert
2022-03-16T22:16:36-85d68bc-4aa1efe/dragonfly-amd64
2022-03-16T21:19:09-fb5dfde-ed4db86/dragonfly-amd64
2022-03-16T21:19:09-fb5dfde-4aa1efe/dragonfly-amd64
2022-03-16T16:07:26-77aa08b-33e752e/dragonfly-amd64
2022-03-16T15:40:39-77aa08b-95395fd/dragonfly-amd64
2022-03-16T07:03:20-77aa08b-5fd0ed7/dragonfly-amd64
2022-03-16T01:41:57-77aa08b-88be85f/dragonfly-amd64
2022-03-16T01:41:57-77aa08b-6e49c59/dragonfly-amd64
2022-03-16T00:34:27-6799a7a-6e49c59/dragonfly-amd64
2022-03-16T00:34:15-6799a7a-1cb34fb/dragonfly-amd64
2022-03-15T20:06:05-6799a7a-0d71234/dragonfly-amd64
2022-03-15T18:37:49-6799a7a-db3045b/dragonfly-amd64
2022-03-15T13:54:34-6799a7a-e475cf2/darwin-amd64-11_0
2022-03-15T00:19:35-54a569a-41a82aa/dragonfly-amd64
2022-03-15T00:13:15-54a569a-15728ce/dragonfly-amd64
2022-03-14T21:01:25-40370f8-88be85f/netbsd-arm64-bsiegert
2022-03-14T20:05:58-dff7c5f-41fe746/dragonfly-amd64
2022-03-14T14:50:06-49d48a0-7dd10d4/netbsd-arm64-bsiegert
2022-03-14T11:03:14-198cae3-7900576/dragonfly-amd64
2022-03-14T09:19:01-198cae3-ab0f761/dragonfly-amd64
2022-03-13T21:31:06-198cae3-3c2e73c/dragonfly-amd64
2022-03-12T23:32:36-198cae3-842d37e/dragonfly-amd64
2022-03-11T21:51:20-ee31f70-baf61e4/dragonfly-amd64
2022-03-11T06:03:26-ee31f70-c1f2213/dragonfly-amd64
2022-03-11T06:00:18-ee31f70-fe75fe3/dragonfly-amd64
2022-03-11T05:06:51-ee31f70-ef7d041/dragonfly-amd64
2022-03-10T23:20:43-ee31f70-7de0c90/dragonfly-amd64
2022-03-10T23:06:14-622cf7b-5003ed8/dragonfly-amd64
2022-03-10T22:50:41-622cf7b-7de0c90/netbsd-arm64-bsiegert
2022-03-10T21:45:24-c773560-914195c/dragonfly-amd64
2022-03-10T21:10:30-613589d-914195c/dragonfly-amd64
2022-03-10T19:30:33-9f99e95-2e46a0a/dragonfly-amd64
2022-03-10T18:50:50-9f99e95-8cf1169/dragonfly-amd64
2022-03-10T18:38:22-9f99e95-91daaab/dragonfly-amd64
2022-03-10T17:32:03-7b442e3-91daaab/dragonfly-amd64
2022-03-10T16:24:16-1670aad-2d026a4/dragonfly-amd64
2022-03-10T16:06:29-1670aad-1cf6770/dragonfly-amd64
2022-03-10T09:12:04-1670aad-5a040c5/dragonfly-amd64
2022-03-10T01:57:27-1670aad-00535b8/dragonfly-amd64
2022-03-10T01:34:17-1670aad-604140d/dragonfly-amd64
2022-03-09T23:03:58-1670aad-7dd10d4/dragonfly-amd64
2022-03-09T22:54:42-fd72fd6-e189b5e/dragonfly-amd64
2022-03-09T17:16:12-03d333a-7026eeb/dragonfly-amd64
2022-03-08T22:23:42-b59c441-0add064/dragonfly-amd64
2022-03-08T22:10:32-b59c441-4469557/dragonfly-amd64
2022-03-08T16:50:57-b59c441-d3070a7/dragonfly-amd64
2022-03-08T02:01:53-b59c441-31be628/dragonfly-amd64
2022-03-07T06:23:26-e155b03-82a6529/dragonfly-amd64
2022-03-04T19:55:36-e562276-7dd10d4/dragonfly-amd64
2022-03-04T18:50:03-121d1e4-797e889/dragonfly-amd64
2022-03-04T18:03:16-19fe2d7-ca384f7/dragonfly-amd64
2022-03-04T01:18:57-3ce7728-81767e2/dragonfly-amd64
2022-03-03T18:04:51-09e0201-58804ea/dragonfly-amd64

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/403534 mentions this issue: cmd/godoc: skip TestWeb if waitForServerReady fails

gopherbot pushed a commit to golang/tools that referenced this issue May 2, 2022
This test fails frequently, with a failure mode that is difficult to
diagnose. (golang/go#50436 may help with that eventually.)

For now, skip the test to reduce noise on the build dashboard.

For golang/go#50014.

Change-Id: I182be5c705846631c983bd5b6c51ab90b71a216a
Reviewed-on: https://go-review.googlesource.com/c/tools/+/403534
Reviewed-by: Dmitri Shuralyov <[email protected]>
Run-TryBot: Bryan Mills <[email protected]>
Auto-Submit: Bryan Mills <[email protected]>
gopls-CI: kokoro <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/403849 mentions this issue: cmd/godoc: expand skips in TestWeb

gopherbot pushed a commit to golang/tools that referenced this issue May 4, 2022
After CL 403534, another TestWeb failure was observed in
https://build.golang.org/log/24cca44e99d848317a6bb73b6d15528b500e5643.
This change expands the skips to try to cover more of the cases
where cmd/godoc might hang.

For golang/go#50014.

Change-Id: If3f08da69a68dc00c399b89ffb2c4f049114aeb6
Reviewed-on: https://go-review.googlesource.com/c/tools/+/403849
Auto-Submit: Bryan Mills <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Run-TryBot: Bryan Mills <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
gopls-CI: kokoro <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
@bcmills
Copy link
Contributor Author

bcmills commented May 13, 2022

This test now has skips for these failure modes, so it is no longer a release-blocker.

@dmitshur dmitshur removed their assignment May 17, 2022
@bcmills bcmills modified the milestones: Go1.19, Backlog Jun 1, 2022
@abhishekdighePersIbm1
Copy link

abhishekdighePersIbm1 commented Aug 11, 2022

Hello Team,

I am facing issue mentioned below

--- FAIL: TestWeb (7.99s)
--- FAIL: TestWeb/GOPATH (1.44s)
godoc_test.go:423: GET http://127.0.0.1:46541/src/fmt/: wanted substring "scan_test.go" in body
godoc_test.go:446: GET http://127.0.0.1:46541/src/fmt/: got:
Let me know if there is any progress/solution?

gopherbot pushed a commit to golang/tools that referenced this issue Nov 21, 2022
The function is derived from the testenv.Command function in the main
repo as of CL 446875, with a couple of modifications to allow it to
build (with more limited functionality) with Go versions as old as
1.16 (currently needed in order to test gopls with such versions).

testenv.Command sets up an exec.Cmd with more useful termination
behavior in the context of a test: namely, it is terminated with
SIGQUIT (to get a goroutine dump from the subprocess) shortly before
the test would otherwise time out.

Assuming that the test logs the output from the command appropriately,
this should make deadlocks and unexpectedly slow operations easier to
diagnose in the builders.

For golang/go#50014.
Updates golang/go#50436.

Change-Id: I872d4b24e63951bf9b7811189e672973d366fb78
Reviewed-on: https://go-review.googlesource.com/c/tools/+/377835
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Joedian Reid <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
Auto-Submit: Bryan Mills <[email protected]>
Run-TryBot: Bryan Mills <[email protected]>
Reviewed-by: Robert Findley <[email protected]>
gopls-CI: kokoro <[email protected]>
gopherbot pushed a commit to golang/tools that referenced this issue Nov 21, 2022
- Use testenv.Command to obtain Cmd instances that terminate (with
  useful goroutine dumps!) before the test's timeout, and remove
  arbitrary hard-coded timeouts.

- Execute the test binary itself as cmd/godoc instead of invoking (and
  cleaning up after) 'go build'.

- Use context cancellation to reduce the number of ad-hoc goroutines
  and channels needed by the tests and to provide stronger invariants
  on process cleanup.

For golang/go#50014

Change-Id: I19ae4d10da691db233c79734799ae074ffdf6a03
Reviewed-on: https://go-review.googlesource.com/c/tools/+/377836
Run-TryBot: Bryan Mills <[email protected]>
Reviewed-by: Joedian Reid <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
gopls-CI: kokoro <[email protected]>
Auto-Submit: Bryan Mills <[email protected]>
@bcmills
Copy link
Contributor Author

bcmills commented Nov 21, 2022

Using x/tools/internal/testenv CL 50014 should produce better diagnostics in case of hang. If that exposes any other failure modes we can handle those as separate issues.

@bcmills bcmills closed this as completed Nov 21, 2022
@golang golang locked and limited conversation to collaborators Nov 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure. Tools This label describes issues relating to any tools in the x/tools repository.
Projects
None yet
Development

No branches or pull requests

5 participants