go
go copied to clipboard
Published
2 weeks ago
•
golang
golang
x/tools/gopls/internal/lsp/cache: unrecognized failures
#!watchflakes
post <- pkg == "golang.org/x/tools/gopls/internal/lsp/cache" && test == ""
Issue created automatically to collect these failures.
Example (log):
signal: segmentation fault
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "golang.org/x/tools/gopls/internal/lsp/cache" && test == ""
2023-01-25 23:57 darwin-amd64-11_0 tools@82707575 go@4df10fba x/tools/gopls/internal/lsp/cache (log)
signal: segmentation fault
2023-01-25 23:57 darwin-amd64-11_0 tools@82707575 go@cea70301 x/tools/gopls/internal/lsp/cache (log)
signal: segmentation fault
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "golang.org/x/tools/gopls/internal/lsp/cache" && test == ""
2023-01-25 23:57 darwin-amd64-10_15 tools@82707575 go@4df10fba x/tools/gopls/internal/lsp/cache (log)
signal: segmentation fault
2023-01-25 23:57 darwin-amd64-10_15 tools@82707575 go@cea70301 x/tools/gopls/internal/lsp/cache (log)
signal: segmentation fault
Found new dashboard test flakes for:
#!watchflakes
post <- pkg == "golang.org/x/tools/gopls/internal/lsp/cache" && test == ""
2023-01-31 21:23 windows-arm64-11 tools@407bbed8 go@ac7efcb0 x/tools/gopls/internal/lsp/cache [build] (log)
vet.exe: failed to write analysis facts: write $WORK\b441\vet.out: There is not enough space on the disk.
golang.org/x/tools/gopls/internal/lsp/cmd.test: write C:\Users\gopher\AppData\Local\Temp\go-build956084258\b448\importcfg.link: There is not enough space on the disk.
golang.org/x/tools/gopls/internal/lsp/cmd: write C:\Users\gopher\AppData\Local\Temp\go-build956084258\b447\vet.cfg: There is not enough space on the disk.
The ones from last week are just "signal: segmentation fault" with no further information, which makes me suspect a problem with the builder or Go toolchain rather than the x/tools code.
The report from an hour ago is a disk-full condition on the Windows builder. Possibly related to the recent filecache deletion bug, since fixed. Perhaps the fix doesn't work on Windows?
