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
encoding/xml: crash on android/arm64 due to https://go.dev/cl/417062 #53814
Comments
It's a guess anyway, since that test caused problems on |
It looks like it also broke at least |
Bah, these tests are a bit too memory intensive. This was discussed on the internal reviews but we didn't really have a way of testing it since there are no internal trybots (yet.) I think the test can just be rewritten to avoid this issue, at the expense of making the limit non-const. |
This failure isn't specific to android/arm64. The test could fail on any machine with limited memory and that platform just happens to expose it. |
@rolandshoemaker Do you plan to work on this before the release? |
Yup, will do. |
Change https://go.dev/cl/417655 mentions this issue: |
Should we backport this? The android-amd64 builder are failing on the 1.17 and 1.18 release branches without this. Thanks. cc @golang/release |
@cherrymui Sure, I think the backport request can be approved trivially. It's a test-only skip, very safe, needed for passing builders on the release branches. |
@gopherbot please backport this. This causes failures on release branches and is a test-only skip. |
Backport issue(s) opened: #54127 (for 1.17), #54128 (for 1.18). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/421094 mentions this issue: |
… tests TestCVE202230633 uses a bunch of memory, and the input cannot be feasibly reduced while maintaining the behavior hasn't regressed. This test could be reasonably removed, but I'd rather keep it around if we can. Updates #53814. Fixes #54128. Change-Id: Ie8b3f306efd20b2d9c0fb73122c26351a55694c4 Reviewed-on: https://go-review.googlesource.com/c/go/+/417655 Run-TryBot: Roland Shoemaker <roland@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> (cherry picked from commit 783ff7d) Reviewed-on: https://go-review.googlesource.com/c/go/+/421094 Reviewed-by: Cherry Mui <cherryyz@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
TestCVE202230633 uses a bunch of memory, and the input cannot be feasibly reduced while maintaining the behavior hasn't regressed. This test could be reasonably removed, but I'd rather keep it around if we can. Fixes golang#53814 Change-Id: Ie8b3f306efd20b2d9c0fb73122c26351a55694c4 Reviewed-on: https://go-review.googlesource.com/c/go/+/417655 Run-TryBot: Roland Shoemaker <roland@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
This appears to be a crash in a test introduced by that CL.
CC @golang/security
The text was updated successfully, but these errors were encountered: