Boost C++ Libraries: Ticket #1417: Regresson tests hang in Darwin (Tiger)

jrp@… — Tue, 06 Nov 2007 22:06:43 GMT

Hmmm. The tests do eventually time out -- capture output fails:

  g++ -dynamiclib -L"/System/Library/Frameworks/Python.framework/Versions/2.5/lib" -L"/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config" -o "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args_ext.so" "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.o" "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/build/darwin/debug/libboost_python-d-1_35.dylib"  -lpython2.5    -g
capture-output /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args
    DYLD_LIBRARY_PATH=/System/Library/Frameworks/Python.framework/Versions/2.5/lib:/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config:/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/build/darwin/debug:/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug:$DYLD_LIBRARY_PATH
export DYLD_LIBRARY_PATH
    PYTHONPATH=/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug
export PYTHONPATH
 /System/Library/Frameworks/Python.framework/Versions/2.5/bin/python "../libs/python/test/args.py"   > "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.output" 2>&1
    status=$?
    echo >> "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.output"
    echo EXIT STATUS: $status >> "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.output"
    if test $status -eq 0 ; then
        cp "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.output" "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args"
    fi
    verbose=0
    if test $status -ne 0 ; then
        verbose=1
    fi
    if test $verbose -eq 1 ; then
        echo ====== BEGIN OUTPUT ======
        cat "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args.output"
        echo ====== END OUTPUT ======
    fi
    exit $status
300 second time limit exceeded
...failed capture-output /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/args.test/darwin/debug/args...
MkDir1 /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test
    mkdir "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test"
MkDir1 /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin
    mkdir "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin"
MkDir1 /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug
    mkdir "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug"
darwin.compile.c++ /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug/raw_ctor.o
    "g++"  -ftemplate-depth-128 -O0 -fno-inline -Wall -g -fPIC -dynamic -Wno-long-double -no-cpp-precomp  -DBOOST_ALL_NO_LIB=1  -I".." -I"/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5" -c -o "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug/raw_ctor.o" "../libs/python/test/raw_ctor.cpp"
darwin.link.dll /Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug/raw_ctor_ext.so
    g++ -dynamiclib -L"/System/Library/Frameworks/Python.framework/Versions/2.5/lib" -L"/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config" -o "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug/raw_ctor_ext.so" "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/test/raw_ctor.test/darwin/debug/raw_ctor.o" "/Users/jrp/boost/regression/results/boost/bin.v2/libs/python/build/darwin/debug/libboost_python-d-1_35.dylib"  -lpython2.5    -g

Tue, 06 Nov 2007 23:00:28 GMT

Groping slightly in the dark, I came across this http://developer.apple.com/releasenotes/DeveloperTools/RN-dyld/index.html which points to a number of known issues:

weak symbols are too expensive
C++ uses weak symbols to tell ld and dyld to coalesce. Any weak external symbols in a linkage unit will cause dyld to do extra work to assure there is only one copy of that symbol in the process. The current implementation uses an O(n^2) algorithm.
No fast thread local storage
pthread_getspecific() is currently the only option
No dl* way to load memory based mach-o images
NSCreateObjectFileFromMemory is deprecated. Some programs decrypt or synthesize mach-o files in-memory. There should be a dl* based API which can use a mach-o file that exists only in memory and not on disk.
Spurious “(com.apple.dyld): Throttling respawn:“ messages in Console
If you alter or replace an OS dylib that participates in the dyld shared cache, dyld will continually try to update the shared cache. But the rebuilt shared cache will not take effect until you reboot. Until the reboot, launchd may throttle (pause) update_dyld_shared_cache.

I don't know whether Boost uses dylib.

Noel Belcourt — Sat, 26 Jan 2008 20:24:22 GMT

Is this still an issue? By that, I mean the fact that the link phase times out is really out of the build systems control. Do the tests actually hang or does this one link step hang for 300s then terminate and the regression tests pick up and continue?

I'm trying to figure out if there's a problem in the bjam sub-process control or not?

jrp at dial dot pipex dot com — Mon, 28 Jan 2008 21:28:17 GMT

Yes, the tests continue after a timeout. The python tests seem to be the most problematic. See, eg, http://tinyurl.com/2w755x

This is Darwin 10.5.1

anonymous — Sat, 09 Feb 2008 05:40:40 GMT

Replying to jrp at dial dot pipex dot com:

Yes, the tests continue after a timeout. The python tests seem to be the most problematic. See, eg, http://tinyurl.com/2w755x

This is Darwin 10.5.1

Okay, I don't yet have Leopard, but there definitely was an occasional hang in the nightly Boost test on PowerPC Tiger (10.4.11) hardware. This is the vfork issue and has been fixed in the trunk. I have never seen the hang on Intel hardware.

I'll leave this ticket open for a bit longer. Please let me know if you have any other data on this issue.

-- Noel

jrp at dial dot pipex dot com — Sat, 09 Feb 2008 15:05:59 GMT

Well all I can tell you is that the full boost regression test suite takes about 400m to run, of which only 120m is user time. So there is a lot of waiting for timeouts going on. http://tinyurl.com/2wxvse is another test that seems to hang, eg. (Passes but does not seem to terminate in time.)

René Rivera — Fri, 20 Jun 2008 04:57:43 GMT

Is there a reliably reproducible instance of where the hanging occurs? Now that I have a 10.5.3 x86 machine I can try and replicate this. But running all the regression tests is not feasible at the moment.

status changed; resolution set

René Rivera — Tue, 01 Jul 2008 13:55:23 GMT

status new → closed
resolution → invalid

Giving up without test case.