x/tools/gopls/internal/regtest/workspace: 失败,未满足“完成初始工作空间加载”的条件,

bjp0bcyl  于 4个月前  发布在  Go
关注(0)|答案(3)|浏览(52)
--- FAIL: TestFilters (27.91s)
    --- FAIL: TestFilters/module_root (27.91s)
        --- FAIL: TestFilters/module_root/experimental (25.12s)
            runner.go:316: waiting on:
                	Unmet: completed work "diagnosing initial workspace load" 1 times
                
                err:context deadline exceeded
                
                state:
                #### log messages (see RPC logs for full text):
                	Info: "2022/01/12 18:58:13 go env for C:\\Users\\gopher\\...
                	Info: "2022/01/12 18:58:31 go/packages.Load\n\tsnapshot=0...
                
                #### diagnostics:
                
                #### outstanding work:
                	Load: 0.00
                	diagnosing initial workspace load: 0.00
                	Setting up workspace: 0.00
                #### completed work:
            runner.go:312: closing editor: Shutdown: context deadline exceeded

greplogs --dashboard -md -l -e 'FAIL: TestFilters'
2022-01-12T19:47:40-d7a4bb4-f005df8/windows-arm64-10
然后,受 #49209 影响的构建器上有很多 openbsd-386 失败,我认为我们可以安全地忽略它们:
2022-01-12T01:49:33-d7a4bb4-3d3f5d9/openbsd-386-70-n2d
2022-01-11T18:17:05-d7a4bb4-a20724d/openbsd-386-70-n2d
2022-01-11T01:22:53-52e9527-9de1ac6/openbsd-386-70-n2d
2022-01-10T04:23:42-94bfe68-6df0957/openbsd-386-70-n2d
2022-01-09T18:43:51-94bfe68-2639f2f/openbsd-386-70-n2d
2022-01-08T00:24:25-94bfe68-90860e0/openbsd-386-70-n2d
2022-01-07T17:27:56-94bfe68-9de1ac6/openbsd-386-70-n2d
2022-01-07T06:34:04-351aaa6-11b28e7/openbsd-386-70-n2d
2022-01-07T05:34:58-351aaa6-9de1ac6/openbsd-386-70-n2d
2022-01-07T01:36:17-a1300ed-c1e7c51/openbsd-386-70-n2d
2022-01-06T21:41:55-a1300ed-9de1ac6/openbsd-386-70-n2d
2022-01-06T16:18:51-4754748-dbdf055/openbsd-386-70-n2d
2022-01-06T00:26:47-04daf88-b5bfaf4/openbsd-386-70-n2d
2022-01-05T21:22:03-04daf88-2b39d86/openbsd-386-70-n2d
2022-01-05T09:50:29-15409b5-2c58bb2/openbsd-386-70-n2d
2022-01-05T01:53:39-15409b5-301db3f/openbsd-386-70-n2d
2022-01-04T20:54:25-15409b5-1242f43/openbsd-386-70-n2d
2022-01-03T23:45:12-ee1ca4f-95b240b/openbsd-386-70-n2d
2022-01-02T14:27:43-ee1ca4f-c886143/openbsd-386-70
2021-12-29T20:20:32-ee1ca4f-6178d25/openbsd-386-70-n2d
2021-12-28T19:29:29-ee1ca4f-1242f43/openbsd-386-70-n2d
2021-12-23T20:03:38-8d38310-b357b05/openbsd-386-70-n2d
2021-12-23T18:58:36-8d38310-af3b8cf/openbsd-386-70-n2d
2021-12-22T18:43:55-8d38310-0f3becf/openbsd-386-70-n2d
2021-12-16T11:15:33-8d38310-de690c2/openbsd-386-70-n2d
2021-12-15T23:51:57-c6ae451-6e7c691/openbsd-386-70-n2d
2021-12-15T16:50:15-c6ae451-de690c2/openbsd-386-70-n2d
2021-12-15T00:33:55-27fc764-9d0ca26/openbsd-386-70
2021-12-15T00:33:55-27fc764-9d0ca26/openbsd-386-70-n2d
2021-12-13T22:45:26-27fc764-5b9207f/openbsd-386-70-n2d
2021-12-12T06:14:07-27fc764-9c6e8f6/openbsd-386-70-n2d
2021-12-10T19:26:50-27fc764-766f89b/openbsd-386-70-n2d
2021-12-09T17:16:12-27fc764-78b4518/openbsd-386-70-n2d
2021-12-09T15:47:16-27fc764-de690c2/openbsd-386-70-n2d
2021-12-09T13:07:36-3fca6a0-48d9489/openbsd-386-70-n2d
2021-12-08T23:38:20-3fca6a0-d6c4583/openbsd-386-70-n2d
2021-12-08T18:30:00-3fca6a0-61011de/openbsd-386-70-n2d
2021-12-08T16:15:56-3fca6a0-61317ef/openbsd-386-70-n2d
2021-12-08T04:14:00-fd2bfb7-a19e72c/openbsd-386-70-n2d
2021-12-07T20:13:17-d3358c1-61317ef/openbsd-386-70-n2d
2021-12-07T03:44:02-feb39d0-dc65c48/openbsd-386-70-n2d
2021-12-06T16:11:25-feb39d0-0f2d0d0/openbsd-386-70-n2d
2021-12-04T04:50:55-c882a49-549cfef/openbsd-386-70-n2d
2021-12-03T18:55:11-c882a49-c4a8550/openbsd-386-70-n2d
2021-12-03T18:55:11-c882a49-0f2d0d0/openbsd-386-70-n2d
x1e47f

ux6nzvsh

ux6nzvsh1#

这个现象似乎与构建者特定有关,而不是测试特定;可能是测试运行器基础设施中的一个错误?

$x_1a^0b^1x$

$x_1m^0n^1x$

$x_1e^0f^1x$

lmvvr0a8

lmvvr0a82#

这意味着gopls在这些构建器上的初始工作空间负载超时了:
请考虑以下日志摘录:

[Trace - 18:08:14.808 PM] Received notification '$/progress'.
Params: {"token":"6426100070888298971","value":{"kind":"begin","title":"Load","message":"Loading query=[builtin mod.com/...]"}}

...

[Trace - 18:08:32.828 PM] Received notification '$/progress'.
Params: {"token":"7981306761429961588","value":{"kind":"end","message":"Finished loading packages."}}

我认为一个合理的下一步是添加围绕加载的额外仪器:go list 花费的时间与其他加载阶段相比如何。

j1dl9f46

j1dl9f463#

https://golang.org/cl/380497提到了这个问题:internal/lsp/regtest: eliminate arbitrary timeouts

相关问题