-
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/benchmarks/sweet/cmd/sweet: TestSweetEndToEnd failing with gvisor build errors since CL 386698 #51445
Comments
cc @mknyszek |
The secondary issue here is that we are apparently not logging the stderr output from the go command, so the actual error is missing. |
This is failing due to https://go.dev/cl/388376 [1]. gVisor has negative go1.19 build tags due to a limitation in their static analysis tool. We'll need to disable this benchmark until gVisor is updated. [1] I don't understand why this CL wasn't specifically tested on https://build.golang.org/?repo=golang.org%2fx%2fbenchmarks. |
Change https://go.dev/cl/389754 mentions this issue: |
Change https://go.dev/cl/389774 mentions this issue: |
Upstream Go tip has updated its version to 1.19, so we need to bump these build tags to allow tip testing. Ideally we'll get checklinkname (or equivalent) to check these remaining unsafe uses (like internal struct field offsets) soon. For golang/go#51445. PiperOrigin-RevId: 432215030
gVisor currently does not build with Go 1.19, so exclude it from "all", "default", and integration testing until it is fixed. It can still be requested explicitly with -run=gvisor. For golang/go#51445. Change-Id: Ib839899af169ff247aa59f264c7891e16784603c Reviewed-on: https://go-review.googlesource.com/c/benchmarks/+/389754 Trust: Michael Pratt <[email protected]> Run-TryBot: Michael Pratt <[email protected]> Reviewed-by: Bryan Mills <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
We use cmd.Output in order to capture stderr, but ExitError.Error doesn't actually include stderr in the string. Create a wrapper error that does so. For golang/go#51445. Change-Id: I5101389c758897e96faa74ef49e9800db1758586 Reviewed-on: https://go-review.googlesource.com/c/benchmarks/+/389774 Trust: Michael Pratt <[email protected]> Run-TryBot: Michael Pratt <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Bryan Mills <[email protected]>
https://go.dev/cl/389754 fixes the builders by disabling the gvisor benchmark. Keeping this open to track reenabling the benchmarks once google/gvisor#7252 goes in. |
Upstream Go tip has updated its version to 1.19, so we need to bump these build tags to allow tip testing. This CL bumps the minimum version in pkg/sync/runtime_amd64.s from 1.8 to 1.14. The offset was different prior to Go 1.14. Ideally we'll get checklinkname (or equivalent) to check these remaining unsafe uses (like internal struct field offsets) soon. For golang/go#51445. PiperOrigin-RevId: 433304124
Change https://go.dev/cl/390954 mentions this issue: |
Change https://go.dev/cl/390955 mentions this issue: |
google/gvisor@adc7bb5 includes https://gvisor.dev/pr/7252, which allows gVisor to build with a Go 1.19 toolchain. For golang/go#51445. Change-Id: I9f352d1bdd2bf57a4dc91bac989d14d3a08db6c0 Reviewed-on: https://go-review.googlesource.com/c/benchmarks/+/390954 Trust: Michael Pratt <[email protected]> Run-TryBot: Michael Pratt <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Michael Knyszek <[email protected]>
Change https://go.dev/cl/391194 mentions this issue: |
Unfortunately still failing at head (https://build.golang.org/log/65cac28815309e7fe290362018f8929ca2204c58):
|
This reverts CL 390955. Reason for revert: benchmark is still failing on longtest builders. Updates golang/go#51445. Change-Id: I35a057933231e89e5b56810ff39c73f3702fd383 Reviewed-on: https://go-review.googlesource.com/c/benchmarks/+/391194 Trust: Bryan Mills <[email protected]> Run-TryBot: Bryan Mills <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Michael Pratt <[email protected]>
What's the status on this? The x/benchmarks repo isn't failing at this point. Is the gvisor benchmark still disabled? If so, we should retitle this to make it about re-enabling this benchmark. |
The current status is that after the previous fix (https://go.dev/cl/390954) there were still failures, so the benchmark was disabled again. This needs to be investigated again, I believe. |
I had labeled this as a release-blocker because the builders were failing, but now the benchmark is disabled and the builder is passing, so it won't mask any other regressions and from my perspective isn't as urgent. Is it important to re-enable this benchmark for the Go 1.19 release, or should we remove the release-blocker label? |
I don't think there's any particular reason fixing this should be tied to the release cycle. I think putting it in Unreleased makes sense. |
I've tested the latest gVisor. It is currently blocked on google/gvisor#7930, which causes us to see spurious SIGKILL exit status. |
Change https://go.dev/cl/444758 mentions this issue: |
Now we are blocked on google/gvisor#8111. :( |
gVisor currently does not build with Go 1.19, so exclude it from "all", "default", and integration testing until it is fixed. It can still be requested explicitly with -run=gvisor. For golang/go#51445. Change-Id: Ib839899af169ff247aa59f264c7891e16784603c
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
google/gvisor@adc7bb5 includes https://gvisor.dev/pr/7252, which allows gVisor to build with a Go 1.19 toolchain. For golang/go#51445. Change-Id: I9f352d1bdd2bf57a4dc91bac989d14d3a08db6c0
This reverts CL 389754. Following CL 390954, our gVisor build is compatible with Go 1.19. Fixes golang/go#51445. Change-Id: Ideee154c48b24cd28af213833aeacdeb60fc4408
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
We use cmd.Output in order to capture stderr, but ExitError.Error doesn't actually include stderr in the string. Create a wrapper error that does so. For golang/go#51445. Change-Id: I5101389c758897e96faa74ef49e9800db1758586
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
This reverts CL 390955. Reason for revert: benchmark is still failing on longtest builders. Updates golang/go#51445. Change-Id: I35a057933231e89e5b56810ff39c73f3702fd383
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
This reverts CL 389754. Following CL XXX, our gVisor build is compatible with Go 1.19. Fixes golang/go#51445. Change-Id: Ideee154c48b24cd28af213833aeacdeb60fc4408
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
Update gVisor past the fix to google/gvisor#7930. Fixes golang/go#51445. Change-Id: I1bf4c471dd3375b6223a578b7b29dfc2182de84c
TestSweetEndToEnd
is persistently failing on thelinux-amd64-longtest
andlinux-amd64-perf
builders since CL 386698 (attn @dr2chase, @prattmic, @aclements).greplogs --dashboard -md -l -e 'error: build gvisor for .*: exit status 1'
2022-03-02T20:53:54-55644cf-bcb89fc/linux-amd64-longtest
2022-03-02T20:14:06-55644cf-2cb9e11/linux-amd64-longtest
2022-03-02T20:02:12-55644cf-fc5b64e/linux-amd64-longtest
2022-03-02T18:21:38-55644cf-986b04c/linux-amd64-longtest
2022-03-02T18:06:42-55644cf-a5b8b56/linux-amd64-longtest
2022-03-02T17:47:07-55644cf-6c6a8fb/linux-amd64-longtest
2022-03-02T17:42:53-55644cf-5a03cbd/linux-amd64-longtest
2022-03-02T17:03:04-55644cf-4a13f6f/linux-amd64-longtest
2022-03-02T16:54:21-55644cf-f79a983/linux-amd64-longtest
2022-03-02T11:49:04-55644cf-40e24a9/linux-amd64-longtest
2022-03-02T11:49:04-55644cf-40e24a9/linux-amd64-perf
2022-03-02T11:33:18-55644cf-fd2e1e7/linux-amd64-longtest
2022-03-02T11:33:18-55644cf-fd2e1e7/linux-amd64-perf
2022-03-02T11:28:40-55644cf-bebe9aa/linux-amd64-longtest
2022-03-02T11:28:40-55644cf-bebe9aa/linux-amd64-perf
2022-03-02T11:27:34-55644cf-9f1239b/linux-amd64-perf
2022-03-01T23:49:01-55644cf-6da16b6/linux-amd64-longtest
2022-03-01T23:49:01-55644cf-6da16b6/linux-amd64-perf
2022-03-01T23:20:30-55644cf-aaa3d39/linux-amd64-longtest
2022-03-01T23:20:30-55644cf-aaa3d39/linux-amd64-perf
2022-03-01T22:02:33-55644cf-d40e7bb/linux-amd64-longtest
2022-03-01T22:02:33-55644cf-d40e7bb/linux-amd64-perf
2022-03-01T21:27:42-55644cf-b0db2f0/linux-amd64-longtest
2022-03-01T21:27:42-55644cf-b0db2f0/linux-amd64-perf
2022-03-01T20:52:30-55644cf-f4722d8/linux-amd64-longtest
2022-03-01T20:52:30-55644cf-f4722d8/linux-amd64-perf
2022-03-01T19:46:09-55644cf-d6d2ebb/linux-amd64-longtest
2022-03-01T19:46:09-55644cf-d6d2ebb/linux-amd64-perf
2022-03-01T19:45:51-55644cf-ad52356/linux-amd64-perf
2022-03-01T19:33:00-55644cf-258fc75/linux-amd64-longtest
2022-03-01T19:33:00-55644cf-258fc75/linux-amd64-perf
2022-03-01T18:48:36-55644cf-620a3c0/linux-amd64-longtest
2022-03-01T18:48:36-55644cf-620a3c0/linux-amd64-perf
2022-03-01T18:43:08-55644cf-510ad45/linux-amd64-longtest
2022-03-01T18:43:08-55644cf-510ad45/linux-amd64-perf
2022-03-01T18:13:15-55644cf-d9fd920/linux-amd64-longtest
2022-03-01T18:13:15-55644cf-d9fd920/linux-amd64-perf
2022-03-01T18:12:19-55644cf-d81464e/linux-amd64-perf
2022-03-01T07:36:46-55644cf-2199841/linux-amd64-longtest
2022-03-01T07:36:46-55644cf-2199841/linux-amd64-perf
2022-03-01T07:36:05-55644cf-7c151f3/linux-amd64-perf
2022-03-01T07:35:26-55644cf-6d881da/linux-amd64-perf
2022-03-01T06:01:28-55644cf-4f04e1d/linux-amd64-longtest
2022-03-01T06:01:28-55644cf-4f04e1d/linux-amd64-perf
2022-02-28T22:24:58-55644cf-936c7fb/linux-amd64-perf
The text was updated successfully, but these errors were encountered: