-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls/internal/lsp/cmd/test: TestSignature failures #59895
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-04-28 17:21 darwin-amd64-12_0 tools@ab24b7b9 go@c3c53a2c x/tools/gopls/internal/lsp/cmd/test.TestSignature (log)
|
Found new dashboard test flakes for:
2023-05-02 16:53 darwin-amd64-nocgo tools@2415ce15 go@337dd753 x/tools/gopls/internal/lsp/cmd/test.TestSignature (log)
|
The log above shows a file of size 2418 whose length (8B) and content (2406B) parts look correctly filled, but whose checksum (final 4B) is all zero. All three parts are written in a single call to lockedfile.Write (via io.Copy) using a 3-element io.MultiReader. Because Copy implements the WriterTo shortcut, it allows each element of the MultiReader to write directly to the output Writer (the locked.File) without an intervening buffer. This at least explains why the boundary between filled and zero portions aligns with the MultiReader element boundary just before checksum, though it doesn't explain why zeros were written as opposed to nothing at all. For efficiency (one syscall instead of three) it may be better to allocate a single array instead of using MultiReader. This would likely mask the flakiness we're seeing here, but it still wouldn't explain it or fix the underlying problem. |
Change https://go.dev/cl/492035 mentions this issue: |
Found new dashboard test flakes for:
2023-05-09 17:51 solaris-amd64-oraclerel tools@90e9c659 go@841e99e2 x/tools/gopls/internal/lsp/cmd/test.TestSignature (log)
|
The latest watchflake note is from a very old run (in early May). |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: