-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: OpenFile failures on js/wasm with new 1.24.0 toolchain upgrade of Go 1.23 #71883
Comments
Found new dashboard test flakes for:
2025-02-21 15:23 x_tools-go1.23-js-wasm tools@f95771e6 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 15:31 x_tools-go1.23-js-wasm tools@8b85edcc release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 18:18 x_tools-go1.23-js-wasm tools@23211ff4 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 18:26 x_tools-go1.23-js-wasm tools@f2beb33b release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 18:51 x_tools-go1.23-js-wasm tools@7347766e release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 19:15 x_tools-go1.23-js-wasm tools@4e0c888d release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
|
Found new dashboard test flakes for:
2025-02-21 21:16 x_tools-go1.23-js-wasm tools@1c52ccd3 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 21:16 x_tools-go1.23-js-wasm tools@6e3d8bca release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
|
Found new dashboard test flakes for:
2025-02-21 21:47 x_tools-go1.23-js-wasm tools@3d7c2e28 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
|
@golang/js I'm a bit out of my depth. These failures are only occurring on our 1.23 builder, which is special: gopls always updates its So in this case, the gopls integration tests are probably the only case where the test binary is built with (effectively) GOTOOLCHAIN=go1.24.0, and opening files seems to be broken in this configuration. |
Could this be an interaction between the GOTOOLCHAIN and the move of the |
Found new dashboard test flakes for:
2025-02-21 22:37 x_tools-go1.23-js-wasm tools@5299dcb7 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 22:37 x_tools-go1.23-js-wasm tools@5299dcb7 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cmd.TestWorkspaceSymbol (log)
2025-02-21 22:37 x_tools-go1.23-js-wasm tools@5299dcb7 release-branch.go1.23@22fdd35c x/tools/gopls/internal/lsprpc.TestDebugInfoLifecycle (log)
|
Found new dashboard test flakes for:
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@22fdd35c x/tools/gopls/internal/cmd.TestWorkspaceSymbol (log)
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@22fdd35c x/tools/gopls/internal/lsprpc.TestDebugInfoLifecycle (log)
|
Is this related to #71758 ? |
I got it, the regression was caused by https://go-review.googlesource.com/c/go/+/595797 . Maybe the |
Found new dashboard test flakes for:
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@2aaa3889 x/tools/gopls/internal/cache.TestCaseInsensitiveFilesystem (log)
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@2aaa3889 x/tools/gopls/internal/cmd.TestWorkspaceSymbol (log)
2025-02-21 23:41 x_tools-go1.23-js-wasm tools@274b2375 release-branch.go1.23@2aaa3889 x/tools/gopls/internal/lsprpc.TestDebugInfoLifecycle (log)
|
Yeah, this is indeed related to the new toolchain behavior introduced in Go 1.21, and the wasm builders not yet being updated to handle it. We just haven't really noticed it until now. I filed issue #71902 with the long term fix for the builders. Unfortunately, it might work only after 1.24, and the builder running into this is a 1.23 one. It should be possible to skip the affected tests on js/wasm whenever GO_BUILDER_NAME contains "-go1.23-" as a workaround—perhaps that's a reasonable path forward here given the options we have. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: