Re: [Boost-testing] Test processing changes...

From: David Walthall (walthall_at_[hidden])
Date: 2008-05-12 11:57:40

David Walthall wrote:
> Rene Rivera wrote:
>> Rene Rivera wrote:
>>> I made a slight change to check for this variance (version 
>>> independent) so it should work better now.
>> Noel & David, any problems running the test processing now?
> 
> 
> My run from yesterday resulted in this error:
> 
> Traceback (most recent call last):
>    File "run.py", line 60, in <module>
>      runner(root)
>    File "C:\boost_testing\tools_regression_src\regression.py", line 189, 
> in __init__
>      self.main()
>    File "C:\boost_testing\tools_regression_src\regression.py", line 526, 
> in main
>      getattr(self,action_m)()
>    File "C:\boost_testing\tools_regression_src\regression.py", line 492, 
> in command_regression
>      self.command_collect_logs()
>    File "C:\boost_testing\tools_regression_src\regression.py", line 415, 
> in command_collect_logs
>      self.regression_log
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 72, in __init__
>      self.add_log()
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 83, in add_log
>      self.x(bjam_log.documentElement)
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 111, in x
>      return getattr(self,name)(node,**kwargs)
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 122, in x_build
>      items = self.x(node,type)
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 111, in x
>      return getattr(self,name)(node,**kwargs)
>    File "C:\boost_testing\tools_regression_src\process_jam_log.py", line 
> 177, in x_build_targets
>      path = self.get_child_data(target_node,tag='path').strip()
> AttributeError: 'NoneType' object has no attribute 'strip'
> 
> I'm rerunning it now to see if the error is still there.  However, the 
> python process consumes 500MB-1GB of memory, which causes thrashing on 
> my computer.  (After one hour of running, it has only managed to use <6 
> minutes of cpu time.)

I got the same error on Friday's run.  (I apologize for the slow post, 
it takes about 5 hours to process the results with process_jam_log.py.)

David