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

[Hans Wennborg]

On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote:
> On 31 Jan 2015, at 01:42, Hans Wennborg <hans at chromium.org> wrote:
>> Hi testers,
>>
>> 3.6.0-rc2 was just tagged. Please test and build binaries.
>>
>> The tracking bug for 3.6 blockers is http://llvm.org/pr22374. Please
>> file issues against it.
>>
>> Thanks for helping with the release!
>
> This time I got an error during check-all, on i386-unknown-freebsd10:
>
>     [...]
>     gmake[1]: Entering directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test'
>     Making LLVM 'lit.site.cfg' file...
>     Making LLVM unittest 'lit.site.cfg' file...
>     gmake -C /home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test/../tools/clang/test lit.site.cfg Unit/lit.site.cfg
>     gmake[2]: Entering directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/tools/clang/test'
>     Making Clang 'lit.site.cfg' file...
>     Making Clang 'Unit/lit.site.cfg' file...
>     gmake[2]: Leaving directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/tools/clang/test'
>     ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -s 8192 ; \
>       /usr/local/bin/python /home/dim/llvm-3.6.0/rc2/llvm.src/utils/lit/lit.py -s -v . /home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test/../tools/clang/test )
>     lit.py: lit.cfg:271: note: Did not find llvm-go in /home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/Release/bin
>     lit.py: lit.cfg:195: note: using clang: '/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/Release/bin/clang'
>     lit.py: lit.cfg:332: note: Did not find clang-interpreter in /home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/Release/bin:/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/Release/bin
>     lit.py: run.py:223: note: failed to initialize multiprocessing
>     -- Testing: 20187 tests, 4 threads --
>     Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80..gmake[1]: *** [check-local-all] Killed
>     gmake[1]: Leaving directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test'
>     gmake: *** [check-all] Error 2
>
> 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?

 - Hans