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
runtime: TestAsyncPreempt failed on linux/arm64 and amd64 #35608
Comments
The issue was observed on specific arm64 and amd64 machines only, 'frameless' is interrupted at consistent addresses which are considered to be non-safe every time upon preemption. // arm64 machine // amd64 machine (just for your reference, I haven't made analysis on it) |
I am seeing this in my go-tip snap builds too. |
The functions being tested, although preemptible, may be preemptible only on small ranges of PCs, especially on architectures where we use REGTMP for returning from the injected call. It is possible that in some unlucky runs all the signals land on the non-preemptible ranges. We can relax the test a little bit, making it more preemptible. With CL http://golang.org/cl/208126 and http://golang.org/cl/208217, it will not be a problem. But maybe not this cycle. |
Change https://golang.org/cl/208221 mentions this issue: |
What version of Go are you using (
go version
)?The issue was observed on linux/amd64 as well, so far the initial analysis is made on linux/arm64 only.
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?
build and run package testing with the latest code.
What did you expect to see?
The case pass on all linux/arm64 and linux/amd64 platforms.
What did you see instead?
ok regexp/syntax 0.757s
--- FAIL: TestAsyncPreempt (60.01s)
FAIL
The text was updated successfully, but these errors were encountered: