On Mar 10, 2014, at 10:24 PM, Steve M. Robbins wrote:

On March 10, 2014 07:20:09 PM Steven Watanabe wrote:

The test-type field appears to be broken. It's most

likely a problem with process_jam_log. (The Boost.Build

tests are run separately, and don't use process_jam_log)

So where is process_jam_log run: on my machine or on the one that gathers
uploaded results ? Why would only my machine be affected?

On your machine. Check that process_jam_log, the executable, can be found by run.py. If you capture the git checkout + bjam build, you should also see it build process_jam_log, unless it finds an existing process_jam_log. It may be trying to build it, and fail. You should see something like this in the log (this for master).

# Searching for "bjam" in "/scratch/boost_testing/tools_bb/src/engine"...

# bjam succesfully built in "/scratch/boost_testing/tools_bb/src/engine/bin.linuxx86_64/bjam" location

# Preinstalled "/scratch/boost_testing/process_jam_log" is not found; building one...

# Found "process_jam_log" source directory "/scratch/boost_testing/boost_root/tools/regression/build"

# Building "process_jam_log" ("/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" process_jam_log -d2 -l300)...