Re: [Boost-testing] links to test files on result pages still cvs

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-11-08 13:16:08

Niko Demmel wrote:
> On 08/11/2007 03:42, Aleksey Gurtovoy wrote:
>> Beman Dawes wrote:
>>   
>>> [...]
>>> Yep.
>>>
>>> Try this:
>>>
>>>    cd boost-trunk/tools/regression/xsl_reports/xsl/v2
>>>    grep cvs *.xsl
>>>
>>> You might also grep for sourceforge.
>>>     
>> .. and see http://article.gmane.org/gmane.comp.lib.boost.testing/5013 
>> for the instructions on how to verify your changes locally.
>>   
> 
> 
> Thanks! I was about to ask about that. Unfortunately it isn't perfect, 
> since the parameters passed in the test case have not much to do with 
> the real library paths so I need to do a bit of (informed) guessing.
> 
> The correct url to the svn depends on the source of the results. Am I 
> right assume that the only two possible "tag" parameters passed to the 
> results-page-generating script are "trunk" and "release" and that those 
> shood be mapped to the following?
> 
>     trunk -> http://svn.boost.org/svn/boost/trunk/
>     release -> http://svn.boost.org/svn/boost/branches/release/

Nope :-) Currently the two options used are --tag=trunk and 
--tag=branches/release. You can see how boost_wide_report.py is used in 
the build_results.sh script 
<http://svn.boost.org/trac/boost/browser/trunk/tools/regression/xsl_reports/build_results.sh>.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo