linux dbgutil tinderbox stuck -> backtrace
sbergman at redhat.com
Fri Apr 1 13:23:46 UTC 2016
On 04/01/2016 01:22 PM, Norbert Thiebaud wrote:
> On Fri, Apr 1, 2016 at 2:59 AM, Stephan Bergmann <sbergman at 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
More information about the LibreOffice