[Boost-testing] Massive debug output in develop nightly testing

Subject: [Boost-testing] Massive debug output in develop nightly testing
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2014-11-11 21:27:11

Hi,

Here’s a snippet of output from the nightly testing process.  I looks like someone’s dumping pointer addresses, or something, and an awful lot of them at that.  Rene, could this be related to the new testing capabilities you’re standing up?  Any ideas?

— Noel

# Starting tests ("/scratch/boost_testing/tools_bb/src/engine/bin.linuxx86_64/bjam" "-sBOOST_BUILD_PATH=/scratch/boost_testing:/scratch/boost_testing/tools_bb/src" "-sBOOST_ROOT=/scratch/boost_testing/boost_root" "--boost=/scratch/boost_testing/boost_root" "--boost-build=/scratch/boost_testing/tools_bb/src" "--debug-configuration"  -l300 toolset=gcc -d2 preserve-test-targets=off --dump-tests -m0 -j16 "--build-dir=/scratch/boost_testing/results" >>"/scratch/boost_testing/results/bjam.log" 2>&1)...
# Running Boost.Build tests
# Using bjam binary in '/scratch/boost_testing/tools_bb/src/engine/bin.linuxx86_64'
# Getting test case results out of "/scratch/boost_testing/results/bjam.log"...
boost_root: /scratch/boost_testing/boost_root
locate_root: /scratch/boost_testing/results
*****Warning - missing test path: boost-test(RUN) "timer/inspect" ["always_show_run_output"] :
  (Usually occurs when bjam doesn't know how to make a target)
***ad50fb
***6a0f61
***ea0258
***fffbeb
***ad50fb
***3279aa
***030b83
***cf5785
***fffbeb