llvm dev - Feb 2015 - [LLVMdev] [3.6 Release] RC2 has been tagged, Testing Phase II begins

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

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:

                      -- Testing: 20187 tests, 4 threads --
Testing Time: 250.10s
  Expected Passes    : 19873
  Expected Failures  : 101
  Unsupported Tests  : 213

The hypervisor I'm running on is also much less busy, which is why the
testing time is now just 250 seconds... Virtualization is not always that great
:)

I've also uploaded the resulting binaries to the sftp area:

SHA256 (clang+llvm-3.6.0-rc2-i386-unknown-freebsd10.tar.xz) =
820a4bb750872ae4055cc9bc5305f7e1ef9e77e192812521ee5adfc0d2049461
SHA256 (clang+llvm-3.6.0-rc2-amd64-unknown-freebsd10.tar.xz) =
c6e59552a9c3ca3486d803438594467d7b0f740e36170fc597eec5e0d1a42859

-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/20150131/17f9dc84/attachment.sig>

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?

Thanks,
Hans