-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls/internal/lsp: TestLSP failures #58702
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
Comments
Found new dashboard test flakes for:
2023-02-16 17:09 windows-amd64-race tools@a30296b4 go@518889b3 x/tools/gopls/internal/lsp.TestLSP (log)
2023-02-17 19:56 windows-amd64-race tools@193023cc go@81eda3a3 x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-02-25 00:08 linux-s390x-ibm tools@f98fce20 go@af6bb3f9 x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-02-27 20:01 windows-amd64-race tools@b0fcf2a0 go@e8fbad5d x/tools/gopls/internal/lsp.TestLSP (log)
|
Both of these builders have issues (the windows one is likely #58714, though it's hard to be sure since we're missing logs in output). In any case, closing this as unactionable. |
Found new dashboard test flakes for:
2023-03-01 16:36 windows-amd64-race tools@096bae8f go@4eb3aea2 x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-06 18:12 windows-amd64-race tools@c91d0b88 go@dbdb3359 x/tools/gopls/internal/lsp.TestLSP (log)
|
This comment was marked as outdated.
This comment was marked as outdated.
Actually, looking at the last failure log, there isn't nearly enough information in the log to diagnose the problem — all of the That part, at least, seems actionable: we can improve the test's output enough for the |
Found new dashboard test flakes for:
2023-03-07 18:17 windows-amd64-race tools@75c657b1 go@74a9d283 x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-07 18:17 windows-amd64-race tools@75c657b1 go@73ca5c0d x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-08 01:14 windows-amd64-race tools@dd1e2f66 go@f5c74165 x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-08 01:14 windows-amd64-race tools@dd1e2f66 go@b561ebab x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-13 18:43 windows-amd64-race tools@ae907a4e go@90dde5de x/tools/gopls/internal/lsp.TestLSP (log)
|
Found new dashboard test flakes for:
2023-03-13 18:43 windows-amd64-race tools@243a9484 go@035db07d x/tools/gopls/internal/lsp.TestLSP (log)
|
These new failures look like timeouts. The internal/lsp tests should be fast -- they take ~9s on my laptop. Yet on the windows race builder, they are taking 200-1200s! This suggests to me that the new gopls architecture (perhaps the filecache) is significantly less performant on Windows. CC @adonovan |
Found new dashboard test flakes for:
2023-04-20 16:14 illumos-amd64 tools@240a4dcd go@0d699b6c x/tools/gopls/internal/lsp.TestLSP (log)
2023-04-20 20:04 illumos-amd64 tools@9c9e11f3 go@15c12762 x/tools/gopls/internal/lsp.TestLSP (log)
2023-04-20 20:04 illumos-amd64 tools@9c9e11f3 go@ecf7e00d x/tools/gopls/internal/lsp.TestLSP (log)
2023-04-20 20:04 illumos-amd64 tools@9c9e11f3 go@bdccb85f x/tools/gopls/internal/lsp.TestLSP (log)
|
Illumos failures look like #59950. |
Interesting that the timeouts have not reoccurred on Windows. Need to greplogs to confirm, but perhaps we improved performance sufficiently that this is no longer a problem. Note that the completion timeout is 1m |
Yes, looks like this stopped in mid-march, around the same time as we made many optimizations. Closing this as fixed. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: