-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall: TestRlimit fails on arm7hl Linux in 1.18rc1 #51479
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
CC @tamird |
I don't understand why the kernel is ignoring the requested change. What version of the kernel are you running? |
In the build system where I first saw the issue we have right now this version:
In the virtual machine where I can reproduce it:
Both are the standard packages that Fedora 35 and Fedora 36 ship. |
I think this test is more trouble than it's worth. |
Change https://go.dev/cl/390020 mentions this issue: |
Reopening for 1.18 backport. |
Change https://go.dev/cl/390022 mentions this issue: |
It's more trouble than it's worth. New code should be using x/sys/unix anyhow. Fixes #40564 Fixes #51479 Change-Id: I1c0e13f494380c1565e98359f088af9f52790b79 Reviewed-on: https://go-review.googlesource.com/c/go/+/390020 Trust: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> (cherry picked from commit 1e122e3) Reviewed-on: https://go-review.googlesource.com/c/go/+/390022 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Closed by merging commit 520f0d0 (CL 390022) to release-branch.go1.18. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
While preparing the Fedora package update for the next Go 1.18 release, I found that TestRlimit fails on arm7hl as you can see in this build. You can see the whole build log here in case someone is interested.
But the failure can be reproduce outside the Fedora build system:
I cannot reproduce it with previous versions, so I bet it might be related to this commit.
What did you expect to see?
No failing tests.
What did you see instead?
A failing test.
The text was updated successfully, but these errors were encountered: