-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
cmd/api: test particularly slow in wsl2 #65670
Comments
I think it's well known that accessing a windows filesystem from WSL is quite slow, see "Performance across OS file systems": I don't think there's much for the Go project to do? |
DO NOT SUBMIT Fixes golang#65670 Change-Id: I446734dd4c63b1fbf4dd48e00bef016c52a23914
Change https://go.dev/cl/563335 mentions this issue: |
An idea, how about tcp communication after starting go list? stack trace
|
In wsl2, accessing the Windows file system from WSL is very slow, and the final test execution can be longer than 10 minutes if the degree of parallelism is low. By adding parallelism to make io start faster, the test time in wsl2 was reduced from 700+s to 280+s. Fixes golang#65670 Change-Id: I148b14bbdf009d38e2ade946300c1bab59ea32d1
Change https://go.dev/cl/575297 mentions this issue: |
cc @golang/wsl |
Go version
go version devel go1.23-628b1015b97 Mon Feb 12 07:15:06 2024 +0000 linux/amd64
Output of
go env
in your module/workspace:What did you do?
in wsl2
./all.bash
What did you see happen?
The test time is not too slow compared to windows.
What did you expect to see?
ok cmd/api 971.468s
API check
ok cmd/api 763.277s
in
The text was updated successfully, but these errors were encountered: