RudbekAssociates

Software that works

NOTICE !!

Rudbek stands behind all of the results we produce. However we do NOT stand behind all the colors assigned to the results after they leave our control.
Many of you may not realize that if a developer decides that there is "no possible fix" for a particular compiler/os/system, he requests that the test be marked as an "expected failure" for that system.

So far, so good. Unfortunately, the little rectangle goes from broken or fail to a fail* which would be great except that fail* changes to a OK when all the tests get summarized for the top level page (e.g. Summary: CVS-RC_1_33_0). I guess this makes everyone feel good to have all that green on the front page, but we at Rudbek Associates consider it fraud. Any color but green should be used (why can't fail* propagate upwards as broken and fail do? As soon as Boost changes their policy, we'll remove this notice.

Windows XP Professional
Version 2002
Service Pack 2
2.2GHz Athlon 64 3400+ (1MB L2 cache) 3GB RAM

VC7_1 --- Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
VC8_0 --- Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86

Script that is run
the full logs are uploaded to ftp://rudbek.com/pub/boost/ at the end of the script

del results\*.log
del results\bin\*.exe /s
rem del \boost\lib\*boost*
python regression.py update-source --tag=RC_1_33_0 --user=vawjr >cvsoutput.log
type cvsoutput.log
mgrep -fv .htm(l`%%)^^ cvsoutput.log | mgrep -f ^^'a's'n  >results\cvschanges.log
timestamp >> results.audit
type results\cvschanges.log >>results.audit
count results\cvschanges.log | mgrep 's(1`2`3):'stotal
echo %errorlevel%
if NOT ERRORLEVEL 1 exit /B 5
copy boost\tools\regression\xsl_reports\runner\regression.py . /Y /v
set | mgrep "(binary|source)"
python regression.py setup --tag=RC_1_33_0 --toolsets=vc-7_1,vc-8_0,mingw-3_4_2,vc-8_0-x86_amd64 --bjam-toolset=msvc
python regression.py install --tag=RC_1_33_0 --toolsets=vc-7_1 --bjam-toolset=msvc
python regression.py install --tag=RC_1_33_0 --toolsets=vc-8_0 --bjam-toolset=msvc
python regression.py test --tag=RC_1_33_0 --toolsets=vc-7_1 --bjam-options=--a --monitored
python regression.py test --tag=RC_1_33_0 --toolsets=vc-8_0 --bjam-options=--a --monitored
timestamp >datetime.txt
copy /Y comment.master+regression.bat+comment.mastertrailer+results\cvschanges.log+trailer.master1+datetime.txt+trailer.master2 comment.html
python regression.py collect-logs --tag=RC_1_33_0 --runner=RudbekAssociates  --comment comment.html
python regression.py upload-logs --tag=RC_1_33_0 --runner=RudbekAssociates
rem call v2.bat
cd results
cvs commit -lm "Auto commit after regression run"
del ..\bjam.log
move bjam.log ..
rem del ..\bjamv2.log
rem move bjamv2.log ..
cd ..
exit /B 0

Changes from CVS for this run
I've removed the .html changes from this list beause they shouldn't be affecting results and these two will always be included as I had to change them to configure for my system
M tools/build/v2/user-config.jam
M tools/regression/xsl_reports/runner/regression.py

C tools/build/v2/user-config.jam
C tools/regression/xsl_reports/runner/regression.py
M tools/build/v2/user-config.jam
M tools/regression/xsl_reports/runner/regression.py

TestManager: vawjr@rudbek.com Tests completed UTC 20051208T133316 in Jackson, Wyoming, USA