Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: freebsd/386 flaky TestCgoSignalDeadlock #18598
referenced this issue
Mar 3, 2017
I haven't yet been able to recreate this using gomote with freebsd-386-110. When I run the test using gomote, it takes consistently less than 0.2s. Looking at the times from the failures listed above, I see these times:
So it looks like at at least on ARM, something is making the test take much much longer than expected. There is no FreeBSD ARM gomote. Since the test has a timeout, if something slows it down a lot it is expected to fail.
Since the test calls
Thanks. It looks like while the test is running the system is getting steadily more and more overloaded, and the test blows through the timeout. I note that the test calls
Something I didn't notice before is that every failure on ARM is in the
It would be nice if we could figure out a way to print what other tests are running when this one fails.
I recently dropped
I'm running the freebsd-arm-paulzhol builder with the following parameters:
It's an ARM Cortex-A7 (Allwinner A20) and has only 1G RAM so it's using a swap partition from a magnetic disk. Could that be what is making it extra slow for the tests?
I can provide ssh access if it would help (or I can help debug).