[Boost-testing] process_jam_log failure aborted regression

Subject: [Boost-testing] process_jam_log failure aborted regression
From: Jim Bell (Jim_at_[hidden])
Date: 2014-06-12 10:13:04

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)
Traceback (most recent call last):
   File "run.py", line 83, in <module>
     runner(root)
   File "F:\boost\gcc\develop\tools_regression_src\regression.py", line 
264, in __init__
     self.main()
   File "F:\boost\gcc\develop\tools_regression_src\regression.py", line 
650, in main
     getattr(self,action_m)()
   File "F:\boost\gcc\develop\tools_regression_src\regression.py", line 
616, in command_regression
     self.command_collect_logs()
   File "F:\boost\gcc\develop\tools_regression_src\regression.py", line 
511, in command_collect_logs
     from collect_and_upload_logs import collect_logs
   File 
"F:\boost\gcc\develop\tools_regression_src\collect_and_upload_logs.py", 
line 2