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/gopls/internal/regtest/misc: frequent TestInconsistentVendoring failures on Windows #49646
Comments
Change https://golang.org/cl/364676 mentions this issue: |
This test is probably detecting a real bug that exclusively affects Windows. To avoid masking other bugs, let's skip the test on that platform until the bug is fixed. For golang/go#49646 Change-Id: I38c615d47454ecfd72b416fff2018973b3ae9259 Reviewed-on: https://go-review.googlesource.com/c/tools/+/364676 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>
Ok, looked into this. Here is my analysis. Consider the following section of logs:
In this segment of the logs, we see that asynchronous diagnostics run on a1.go, while the It looks like we can just change the |
The locking behavior would definitely explain the Windows-specific failure mode — file locks on Windows are enforced, whereas on Unix platforms they're only advisory. Switching to |
Change https://go.dev/cl/399714 mentions this issue: |
Running go mod vendor can result in vendor/modules.txt being transiently deleted while it is being updated. On Windows this introduces potential problems with file locking, if modules.txt is being read by another go process, such as an ongoing package load. Change the command to use RunGoCommandPiped, which executes serially within the gopls process. For golang/go#49646 Change-Id: If2d1fe5431122ba05014051a0e9c303cf7ee9cb2 Reviewed-on: https://go-review.googlesource.com/c/tools/+/399714 Run-TryBot: Robert Findley <rfindley@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
Trying to check whether this is resolved, I am running the command above:
@bcmills I get far fewer results than you cited, even when using the master versions of fetchlogs and greplogs. The last match I see is from 2021-09-09. Am I doing something wrong? |
How far back have you fetched |
To be precise, I'm doing the following:
|
Yeah, the default |
Aha, thanks. I think for that reason I was only seeing the older failures in my cache. Now I see the same as you. It seem statistically significant based on the prior frequency that this has not failed since being re-enabled 8 days ago. It might be good to give it another week, but I'm going to close this now so that I don't have to follow up in a week :) If it starts flaking again presumably we'll find an re-open this issue. |
It appears that
go mod vendor
can't deletevendor/modules.txt
because something else in the test is holding it open.(Ideally perhaps
go mod vendor
should overwrite the file in-place instead of deleting and recreating it, but that seems like a separate bug.)greplogs --dashboard -md -l -e 'FAIL: TestInconsistentVendoring'
2021-11-16T19:18:26-8122e49-b954f58/windows-386-2008
2021-11-12T00:16:15-c116b72-7bed3c7/windows-386-2008
2021-11-05T19:01:13-4ab7496-93bab8a/windows-386-2008
2021-11-02T20:34:09-182bbdc-f9cb33c/windows-386-2008
2021-11-02T19:48:11-f6440c8-1011e26/windows-386-2008
2021-10-30T00:47:26-a6c6f4b-d19c5bd/windows-amd64-2016
2021-10-25T23:28:03-f916b54-e9eb66d/windows-amd64-2016
2021-10-25T20:40:31-5a40697-c580180/windows-amd64-race
2021-10-12T22:12:04-94178a2-732f6fa/windows-386-2008
2021-09-21T20:39:31-b98090b-48cf96c/windows-amd64-2016
2021-09-17T23:04:15-2758b04-07b30a4/windows-386-2008
2021-09-15T14:06:14-4ba3eff-e4dfd78/windows-amd64-2016
2021-09-14T19:06:02-258ee27-21a4e67/windows-386-2008
2021-09-09T13:49:11-c163c31-021fc24/windows-amd64-2016
2021-08-20T18:45:25-bf6c7f2-0f25251/windows-arm64-10
2021-08-15T19:56:18-a55d515-717894c/windows-386-2008
2021-08-15T15:51:49-a55d515-48dfddb/windows-386-2008
2021-08-03T16:06:16-594b3a2-7921829/windows-386-2008
2021-08-02T20:16:24-45eff0f-accf363/windows-amd64-race
2021-07-07T16:41:12-7edcfe5-c96833e/windows-amd64-2016
2021-06-30T22:02:09-f0847e0-4711bf3/windows-amd64-2016
2021-05-19T13:04:45-17b3466-658b5e6/linux-arm-scaleway
2021-05-10T21:56:33-0185c7e-07d8cba/linux-arm-scaleway
2021-05-06T19:28:34-c0140e8-07d8cba/linux-arm-scaleway
2021-05-06T03:14:34-08a4f34-ba7cac4/linux-arm-scaleway
2021-05-06T02:57:18-f4a4129-ba7cac4/linux-arm-scaleway
2021-05-05T22:35:07-dd255f2-ba7cac4/linux-arm-scaleway
2021-05-05T21:11:25-68c6cab-ba7cac4/linux-arm-scaleway
2021-05-05T20:44:55-68c6cab-c0a7ecf/linux-arm-scaleway
2021-05-05T01:45:45-7cab0ef-c0a7ecf/linux-arm-scaleway
2021-05-04T19:12:24-f03daea-c0a7ecf/linux-arm-scaleway
2021-05-03T21:45:16-42984c4-72ccabc/linux-arm-scaleway
2021-05-03T20:05:58-19b1717-72ccabc/linux-arm-scaleway
2021-05-03T16:36:24-3e17c62-72ccabc/linux-arm-scaleway
2021-04-30T14:46:28-291330a-72ccabc/linux-arm-scaleway
2021-04-29T13:06:21-28c1392-5aed4ce/linux-arm-scaleway
2021-04-28T21:52:02-800adbe-5aed4ce/linux-arm-scaleway
2021-04-28T19:13:50-16b25d2-ad989c7/linux-arm-scaleway
2021-04-28T01:46:37-16b25d2-06c9756/linux-arm-scaleway
2021-04-27T20:55:22-7c72a84-06c9756/linux-arm-scaleway
2021-04-27T19:53:45-d0768c9-06c9756/linux-arm-scaleway
2021-04-27T15:36:10-6397a11-06c9756/linux-arm-scaleway
2021-04-27T12:58:28-fe1c548-06c9756/linux-arm-scaleway
2021-04-27T04:02:17-735ed62-06c9756/linux-arm-scaleway
2021-04-26T20:11:56-e3dc99f-06c9756/linux-arm-scaleway
CC @findleyr
The text was updated successfully, but these errors were encountered: