Re: linux dbgutil tinderbox stuck -> backtrace

On 03/31/2016 03:17 PM, Norbert Thiebaud wrote:
> On Thu, Mar 31, 2016 at 7:59 AM, Michael Stahl <mstahl@redhat.com> wrote:
> > it's a pretty rare deadlock, i've hit it once and sberg too once AFAIK.

Ah, <https://bugs.documentfoundation.org/show_bug.cgi?id=96387> 
"deadlock in HSQLDB" predates 
<https://cgit.freedesktop.org/libreoffice/core/commit/?id=03a271901c39d60e4519e67e258d565ad5e1e085> 
"Guard against globally shared UNO ref accessed from wrong UNO env", 
which was the only change that came to mind when I saw Norbert's 
original post.

I've started to run into this a couple of times now, too.  But at least 
the one time I was alert enough to run jstack on the deadlocked process, 
all it gave me was an internal failure in jstack.

> What I really wish for is a reliable hard timeout on all these tests.

I think a better approach would be to let the bots do containerized 
builds that get automatically killed after whatever timeout the bot 
maintainer deems reasonable, or passed on to someone who can debug the 
problem, or...