x/tools/gopls/internal/cmd: TestMCP* tests fail on Plan 9

[millerresearch]

TestMCPCommandLogging, TestMCPCommandStdio and TestMCPCommandHTTP can only be run on platforms where fsnotify is supported. This is breaking the x/tools repo build on Plan 9:

gopls: fsnotify not supported on the current platform
*** Test killed with quit: ran too long (11m0s).
signal: killed
--- FAIL: TestMCPCommandLogging (4.91s)
--- FAIL: TestMCPCommandLogging/notrace.log (2.20s)
    mcp_test.go:135: calling "initialize": EOF
--- FAIL: TestMCPCommandLogging/trace.log (2.68s)
    mcp_test.go:135: calling "initialize": EOF
--- FAIL: TestMCPCommandStdio (2.42s)
    mcp_test.go:51: calling "initialize": EOF
FAIL	golang.org/x/tools/gopls/internal/cmd	720.047s

The tests are already skipped on other unsupported platforms because of the lack of execve support.

[gabyhelp]

Related Issues

• x/tools/gopls/internal/cmd: TestMCPCommandStdio fails on platforms without execve (need: testenv.NeedsExec()) #74258
• x/tools/go/packages/packagestest: TestGOPATHExport and TestModulesExport are failing on Plan 9 #46503 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[gopherbot]

Change https://go.dev/cl/688155 mentions this issue: gopls/internal/cmd: disable failing tests on plan9