[PATCH] Increase timeout (ulimit -t) for testing phase
hans at chromium.org
Mon Feb 2 14:15:29 PST 2015
On Mon, Feb 2, 2015 at 1:47 PM, Dimitry Andric <dimitry at andric.com> wrote:
> During testing for 3.6.0 RC2, I was running tests (make check-all) in a VM on a rather busy hypervisor, and they eventually got killed due to the CPU time limit enforced via "ulimit -t 600" in test/Makefile.
> Since more and more tests are added, and this will not stop for the foreseeable future (I hope :), can we please increase the timeout? For example, by doubling it for now, we should be good for quite some time, and for bots it doesn't matter too much whether they time out after 10 or 20 minutes:
Looks like the timeout has been set to 600 s for a very long time
I don't know what others think, but if it's possible to run into it on
a slow machine, raising it seems like a good idea to me.
More information about the llvm-commits