Skip to content

x/tools/gopls/internal/cache: TestZeroConfigAlgorithm failing on wasm builders #65271

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

Closed
bcmills opened this issue Jan 24, 2024 · 1 comment
Closed
Assignees
Labels
arch-wasm WebAssembly issues FrozenDueToAge gopls Issues related to the Go language server, gopls. NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure. Tools This label describes issues relating to any tools in the x/tools repository.
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Jan 24, 2024

Go version

2c35def

Output of go env in your module/workspace:

N/A

What did you do?

View https://ci.chromium.org/p/golang/g/x-tools-gotip/console

What did you see happen?

Failures for all wasm platforms:

--- FAIL: TestZeroConfigAlgorithm (0.43s)
--- FAIL: TestZeroConfigAlgorithm/basic_AdHoc_workspace (0.02s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/basic_GOPATH_workspace (0.04s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/basic_go.mod_workspace (0.06s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/basic_go.work_workspace (0.06s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/go.work_from_env (0.02s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/independent_module_view (0.02s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/multi-folder_workspace (0.02s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/multi-module_workspace (0.03s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/multiple_go.work (0.03s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/multiple_go.work,_c_unused (0.03s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/unified_workspace (0.03s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/zero-config_open_module (0.02s)
    session_test.go:253: fetching env: <nil>
--- FAIL: TestZeroConfigAlgorithm/zero-config_open_modules (0.03s)
    session_test.go:253: fetching env: <nil>
FAIL
FAIL	golang.org/x/tools/gopls/internal/cache	2.264s

What did you expect to see?

All tests either passing or skipped on the configured builders.

I suspect that this test just needs a call to testenv.NeedsGoPackages or similar.

(attn @findleyr)

@gopherbot gopherbot added Tools This label describes issues relating to any tools in the x/tools repository. gopls Issues related to the Go language server, gopls. labels Jan 24, 2024
@gopherbot gopherbot added this to the Unreleased milestone Jan 24, 2024
@bcmills bcmills added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsFix The path to resolution is known, but the work has not been done. arch-wasm WebAssembly issues labels Jan 24, 2024
@suzmue suzmue modified the milestones: Unreleased, gopls/v0.15.0 Jan 25, 2024
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/559155 mentions this issue: gopls/internal/cache: skip TestZeroConfigAlgorithm on wasm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly issues FrozenDueToAge gopls Issues related to the Go language server, gopls. NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure. Tools This label describes issues relating to any tools in the x/tools repository.
Projects
None yet
Development

No branches or pull requests

4 participants