On Thu, Mar 31, 2016 at 8:23 AM, Noel Grandin <noelgrandin@gmail.com> wrote:
Of course, it may be simpler and safer to simply surround the relevant tests
with a brute-force-5-min-timeout-and-kill.
yeah.. except the timeout value should probably be longer or smarter,
or an optional parameter in gbuild invocation for outlier...
we do not want it triggering abusively on slow machines... for ci purpose
even 15 minutes would be tolerable... (and really a test that
'normally' run for longer than that should be split anyway)
beside this is not necessarily a java only issue... on occasion some
other tests not involving java can dead-lock or cpu-loop...
Norbert
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.