-
Notifications
You must be signed in to change notification settings - Fork 18k
x/benchmarks/sweet: disable gvisor for arm64 by default #67869
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
Comments
Seems fine to me, thanks for trying out the benchmarks on arm64. If you're able, please feel free to send a CL (or a PR) to me. See https://go.dev/doc/contribute. Otherwise I'll try to get to it in the near future, but a contribution would be helpful in moving this along faster, if you need it sooner. Thanks. |
Thanks. I'd like to contribute. Let me follow that guide ... |
Similar Issues (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
@haoliu-ampere Are you planning on sending a CL? |
Yes. I'm still waiting for the CLA (maybe some legal concerns). |
Change https://go.dev/cl/601075 mentions this issue: |
Hi @mknyszek, For https://go.dev/cl/601075, it should have been reviewed and voted. But it seems I cannot trigger the Trybots and Submit, could you please help to trigger the test suite and submit the change? Thanks in advance.
|
Sorry for the delay, I've set CQ+1 and Auto-Submit. |
Go version
go version go1.22.3 linux/arm64
Output of
go env
in your module/workspace:GOARCH='arm64'
What did you do?
Currently,
x/benchmarks/sweet
fails to rungvisor
(which is enabled by default) on linux/arm64:./sweet run ...
What did you see happen?
gvisor
only runs on linux/amd64. (see more: golang/benchmarks@34853f5).What did you expect to see?
I think it's reasonable to only enable
gvisor
foramd64
. E.g., a simple patch would be:cc @mknyszek
The text was updated successfully, but these errors were encountered: