[Boost-testing] Re: Re: pjb intel-win32 tests

From: Paul Baxter (pauljbaxter_at_[hidden])
Date: 2005-05-10 18:53:12

> For the Regression testing FAQ/wiki??:

Snipped the bit about adding a suffix to toolsets variables to annotate 
compiler versions as this doesn't work as I described. Don't know how this 
escaped me earlier. (Well I do, I tried adding -8_1 which worked and thought 
it a textual suffix rather than it actually specifying another jamfile 
variant behind the scenes. Penny dropped thanks to Stefan's comments.)

Its made me curious as to why John suggested I amend the toolset name...

John: One other thing that would help, would be to run the tests using an
appropriately named toolset, something like "intel-win32-8.1-release" would
be good.

I think I might be missing something vital here!

Do you mean create a new .jam file for this configuration rather than use 
the defaults in boost\tools\build\v1\intel-win32-8_1 ?

[Note, I was using 'intel-win32' toolset as per the boost website docs until 
Stefan pointed out intel-win32-8_1 which adds no autolinking to the base 
toolset jam file. My next run will include this refinement.Will find out by 
the morning if this affects the results I posted]

Perhaps my question should be what is the difference between boost builds 
notion of a general debug and release set of compiler settings? Just DEBUG 
defined or more substantial. I looked in the Intel_win*.jam tools and didn't 
find any command line differences between each.

What would change between debug and release build that would warrant a 
release-only jam file?

At the risk of even more egg on my face, can you explain a little.

> Q) If I want to submit test results what information do I need to supply?
> A) Look at the basic python regression testing information on the boost 
> web site, and consider the following refinements to make it easier for 
> others to use the information you are supplying:
>
> As well as a basic way of identifying you as a regression tester via a 
> unique setting for the 'runner' command line option, it is helpful for 
> other regression testers/maintainers to understand a little about your 
> platform and compiler.
>
> The file 'comment.html' in your regression testing root directory provides 
> a means to incorporate some descriptive text about your test environment 
> into the final test output that is returned to the boost regression test 
> archive.
>
> Use this to list your platform hardware, OS, compiler(s) and other 
> pertinent setup information.
>
> If you are willing to help out further, it would also be useful to attach 
> contact name and email details for cases where the maintainers of 
> particular tests have further questions.
>

<snipped section on toolset suffixes that was pure fiction>

> For example on WinXP bring up a CMD window and set compiler path, library 
> and include etc. and then use:
>
> -----------------
>
> set BUILD=release
> python regression.py --runner=pjb --toolsets=intel-win32-8_1
>
> -----------------
>
> My comment.html file looks like:
>
> <p>Tests are run on Win32 platform. Intel-win32 release build v8.1.027 on 
> AMD XP 2000+ running latest Win XP 32 bit. Contact: myname at myhost dot 
> com</p>

Addition to above:
Note that there may be some version-specific additions to the toolset name 
needed for your compiler. It is worth looking within the downloaded tarball 
or CVS release in boost\tools\build\v1 for a *.jam that more closely 
represents your configuration. This may refine your choice of toolset name 
and lead to better regression results.