On 04/01/2016 01:22 PM, Norbert Thiebaud wrote:
On Fri, Apr 1, 2016 at 2:59 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
1/ we _do_ have such global level deadlock.. but jenkins being java...
these are unreliable (jenkins plugin that provide that feature even
explain in details that it is unreliable)...
I don't claim Jenkins is a good infrastructure for this. (But I don't
want to start any discussion about that. Just wanted to point out that
adding timeouts to test code is the wrong solution to the underlying
problem of having reliable build bots.)
2/ the linux debug build, once a week also rebuild the doc.. which
takes a long time.. so I had to bump that global level deadlock to the
max time a full build + build the doc and upload it can take... which
make the deadlock kick in the 5-6 hours range... not great.
A single, fixed timeout, independent of the kind of build you're doing,
indeed doesn't look very useful.
[...] or passed on to someone who can debug the problem, or...
There is a flow of task to do.. I cannot block a slave for an
undetermined amount of time waiting for someone to take a look.... or
the build queue piles up...
This depends on how much you can containerize/virtualize the builds, of
course.
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.