[LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins

Dimitry Andric dimitry at andric.com
Mon Feb 2 13:48:10 PST 2015


On 02 Feb 2015, at 22:36, Hans Wennborg <hans at chromium.org> wrote:
> 
> On Sat, Jan 31, 2015 at 11:47 AM, Dimitry Andric <dimitry at andric.com> wrote:
>> On 31 Jan 2015, at 20:24, Hans Wennborg <hans at chromium.org> wrote:
>>> 
>>> On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote:
>> ...
>>>> This is because the ulimit -t 600 was exceeded, as shown in dmesg:
>>>> 
>>>>   pid 78288 (python2.7), uid 1000, was killed: exceeded maximum CPU limit
>>>> 
>>>> Can we bump the -t limit a little?  If a machine is rather busy when doing the tests, this limit can be exceeded.
>>> 
>>> I'd be OK with that. Did the tests pass for you if you raise the limit?
>> 
>> Yes, re-running "gmake check-all" from the rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj subdirectory succeeds now:
> 
> Do you want to send a patch out to the list for raising the timeout?

I've sent a patch to llvm-commits.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150202/22ea0962/attachment.sig>


More information about the llvm-dev mailing list