Boost Testing :
From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2008-05-07 10:32:23
On May 6, 2008, at 10:06 AM, K. Noel Belcourt wrote:
> On May 4, 2008, at 5:28 PM, Rene Rivera wrote:
>> If you fit the above reply on the list which tester IDs you will be
>> switching to the new PJL, so that people don't collide. To switch two
>> things are needed:
>> 1. Get the latest version of "run.py" if you don't update it as
>> part of
>> your testing
>> 2. Add, or replace, "--pjl-toolset=python" when running the tests.
> I could switch over the Sandia-gcc results since there's other
> testers running gcc on linux. Shall I set this up for tonight's runs?
Looks like we had a problem with Sandia-gcc after the tests finished
running. Any idea what happened?
...failed updating 722 targets...
...skipped 2002 targets...
...updated 79353 targets...
...updated 1 target...
# Executing SVN command "svn --non-interactive info --xml "/var/
svn: warning: cannot set LC_CTYPE locale
svn: warning: environment variable LANG is en_US.UTF-8
svn: warning: please check that your locale name is correct
Traceback (most recent call last):
File "run.py", line 60, in ?
line 189, in __init__
line 526, in main
line 492, in command_regression
line 401, in command_collect_logs
from process_jam_log import BJamLog2Results
ImportError: No module named process_jam_log