On 31.03.2016 15:23, Noel Grandin wrote:
On 2016/03/31 3:17 PM, Norbert Thiebaud wrote:
What I really wish for is a reliable hard timeout on all these tests.
Not sure how much it helps, but Java has a built-in thread deadlock detector (which may or may
not fire here, since it
only detects deadlocks where the locks in question are all Java-level locks)
I have code that I can contribute that runs a watchdog thread that queries the Java deadlock
detector every 2 seconds
and kills the program when a deadlock is detected.
hmm... that would help in this particular case, but generally speaking,
this is the first and only java-only deadlock i've ever seen in a test,
usually 2 C++ threads are involved in a deadlock.
Of course, it may be simpler and safer to simply surround the relevant tests with a
brute-force-5-min-timeout-and-kill.
that depends on the build configuration, if you're running the test with
ASAN / valgrind / drmemory the timeout needs to be much longer or disabled.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.