[cfe-dev] [3.6 Release] RC2 has been tagged, Testing Phase II begins

[Dimitry Andric]

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 had this diff for trunk for some time:

Index: test/Makefile
===================================================================
--- test/Makefile       (revision 224612)
+++ test/Makefile       (working copy)
@@ -91,7 +91,7 @@ else # !SunOS
 # its thread-local storage, don't set a limit here.
 # When -v is not used, then -s has to be used to limit the stack size.
 # FIXME: Those limits should be enforced by lit instead of globally.
-ULIMIT=ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -s 8192 ;
+ULIMIT=ulimit -t 1200 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -s 8192 ;
 endif # SunOS

 check-local:: lit.site.cfg Unit/lit.site.cfg

-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/cfe-dev/attachments/20150131/b81fabcf/attachment.sig>