You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excepted kill timeout is test.timeout=3m0s, but in most case the test run more then 3min(4m0s in this case), looks like the parent(PID 23893) has no CPU tick to issue "kill -SIGQUIT" to CgoCallbackGC (PID 24001).
The tests are sized for reasonably powerful machines. If you want to run
the tests in smaller machines you can change the test timeout scale, this
is what I do for my arm machines.
wheelcomplex
changed the title
runtime/trace: test failed(timeout) in low end machine, CgoCallbackGC use up all CPU power
runtime/trace: test failed(timeout/hang) in low end machine, CgoCallbackGC use up all CPU power
Mar 14, 2016
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
all test pass
more info:
Excepted kill timeout is test.timeout=3m0s, but in most case the test run more then 3min(4m0s in this case), looks like the parent(PID 23893) has no CPU tick to issue "kill -SIGQUIT" to CgoCallbackGC (PID 24001).
Is that too many goroutine created from https://github.com/golang/go/blob/master/src/runtime/testdata/testprogcgo/callback.go#L66?
After reduce const P = 100 to const P = 20 everything is OK(ok runtime/trace 41.667s). Maybe a auto-detect P base on runtime.NumCPU() is better?
The text was updated successfully, but these errors were encountered: