-
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
sync: TestWaitGroupMisuse2 takes 45-90 seconds on netbsd, AIX #22944
Comments
/cc @dvyukov for any theories. |
This test requires physical parallelism, so my first bet would be on a problem in netbsd scheduler. |
Perhaps execution trace will sched some light. |
how can I run this specific test? |
|
netbsd's nanosleep always schedules another process, even for really short sleeps. making it spin on really short sleeps fixes this |
NetBSD nanosleep() always sleeps for at least 1 schedule slice when the specified time is under the schedule resolution. With default HZ value of 100 for i386 and amd64, it's always at least 10ms even when the specified time is smaller. I think other systems might work similar way. |
@coypoop, or:
Or:
|
It takes 45 seconds on AIX too, and never panics as it expects to: https://build.golang.org/log/4521fa0230a42f6f3b70e8f108c3ab63d962d567 /cc @Helflym |
I was already aware about this failure. But I didn't find anything relevant. Edit: as NetBSD, it might be related to AIX scheduler:
|
|
TestWaitGroupMisuse2 on Linux with 8 cores takes 0.22s.
On NetBSD it does pass but takes 45-90 seconds. Why?
/cc @bsiegert
The text was updated successfully, but these errors were encountered: