I suspect my issue may have been over-isolation. While I only needed a new process group, I did it by creating a new session. The SIGQUIT used by timeout/gtimeout may not be able to work across sessions.
I'm going to give this another try with just setting the process group without creating a new session. I'll watch that one as well as it goes through the bot. -Todd On Tue, Sep 22, 2015 at 9:09 AM, Todd Fiala <todd.fi...@gmail.com> wrote: > I stopped the two builds in progress (that were badly hanging, 20 minutes > per test run configuration) until the builder caught up to r248284. > > -Todd > > On Tue, Sep 22, 2015 at 9:06 AM, Todd Fiala <todd.fi...@gmail.com> wrote: > >> Rolled back here: >> ➜ lldb svn commit >> Sending test/dosep.py >> Transmitting file data . >> Committed revision 248284. >> >> I'll re-add this and limit to OS X after I get a chance to review. >> >> -Todd >> >> On Tue, Sep 22, 2015 at 9:01 AM, Todd Fiala <todd.fi...@gmail.com> wrote: >> >>> Hey all, >>> >>> On the Linux build bot, I'm seeing at least one test hung here after my >>> change: >>> >>> http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/6572 >>> >>> It is conceivable that my change to put the test inferior into a >>> separate process group is interfering with timeout handling. >>> >>> I'll revert that out and only add it in for OS X where we're primarily >>> seeing the hangup issue. If that addresses the hangs, then I'll need to >>> investigate further. >>> >>> -- >>> -Todd >>> >> >> >> >> -- >> -Todd >> > > > > -- > -Todd > -- -Todd
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
