On 2014-06-12 10:40 AM, Rene Rivera wrote:
I'm trying to think what could be the problem.. Do you know when it started failing?


On Thu, Jun 12, 2014 at 9:13 AM, Jim Bell <Jim@jc-bell.com> wrote:
The develop branch regression shunted at the process_jam_log run. The bjam run seems to have completed normally. I don't think results went up.

Windows7x64, mingw-w64-gcc-4.7:

Here's the relevant output:

F:\boost\gcc\develop\boost_root\status>"F:\boost\gcc\develop\process_jam_log.exe" "F:\boost\gcc\develop\results" 0<"F:\boost\gcc\develop\results\bjam.log"
boost_root: F:/boost\gcc\develop\boost_root
locate_root: F:\boost\gcc\develop\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)

My Windows message logs don't show a crash, so it's probably a non-zero exit code.  Only on the develop branch. Maybe just caught an incomplete commit? I'll check the run tomorrow.