-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
reflect: k8s unit tests on ppc64le sees SEGV fault with tip #48238
Comments
I think modern-go/reflect2 must be changed to adopt the new change to mapiterinit: https://github.com/modern-go/reflect2/blob/333559e1834b0c1840d283d79220bf121d704022/unsafe_link.go#L32 It uses cc @josharian |
cc @taowen |
Putting in the 1.18 milestone just to keep this on the radar for a decision, but if the issue is caused by |
Upstream bug is modern-go/reflect2#24. I'm going to close this issue because there isn't anything to change in the Go repository. (This is an example of why I personally encourage people to avoid using reflect2. It's impossible for us to support that kind of package. Where there are deficiencies in reflect, let's fix them, rather than introducing an unsupportable third party package. Just my opinion, of course.) |
anyone can help to maintain https://github.com/modern-go/reflect2 ? I no longer have the insight to keep up with the language evolution. |
When reading and then subsequently writing a BMH yaml within a bootstrap ignition file we encountered a panic. This seems to be a rather well known issue with these two module versions and upgrading fixes the problem. This was fixed in master by cc8f353 when updating some seemingly unrelated packages, but it seems safer to just updated the required ones rather than also bringing back the prometheus client update. References: golang/go#48238 kubernetes/kubernetes#104947 https://bugzilla.redhat.com/show_bug.cgi?id=2122747
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (
go env
)?Linux ppc64le
go env
OutputWhat did you do?
Installed go and kubernetes using below steps and ran the test for kubernetes
What did you expect to see?
Test passing successfully
What did you see instead
Test panics with the below stack trace, Even observed similar panic on x86 as well.
When I traced the above scenario found a recent change 1b2d794 and the test runs before this commit is successfully passing.
The text was updated successfully, but these errors were encountered: