[Lldb-commits] [PATCH] 5 minute timeout for tests
zturner at google.com
Mon Dec 1 15:27:48 PST 2014
On Mon Dec 01 2014 at 3:19:09 PM Vince Harron <vharron at google.com> wrote:
> Currently when the tests lock up on the build server, the build script
> kills the tests and gets *no* test results. That means that if a bug goes
> in that causes a test to hang, we don't get results for *any* tests.
> Killing the individual test causes it to show up as a FAIL (Chaoren might
> change this to show result as "TIMEOUT")
I see, this wasn't clear before. I understood that the bots would already
kill individual tests that hanged, and not fail the entire test suite.
> It's not really about what tests are hanging today, it's that some day a
> test will hang. When that happens, do we want to lose all test results as
> a result? Look at the Linux buildbot history. Many runs have no test
> results at all. Which test caused the lockup? I have no idea.
> > Both of those options are really undesirable in my opinion.
> We can make the test timeout be an OSX/Linux thing only for now...
How bad would it be to just use psutil? We could integrate it with the
build so that it builds psutil when you build lldb, and deploys it to the
same place that lldb's python module goes so that it's automatically in the
Eventually we're going to need this on other platforms too, and it benefits
everyone if we can share code instead of implementing things differently on
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-commits