Re: [Boost-testing] [crystax.net] Large regression files..

Subject: Re: [Boost-testing] [crystax.net] Large regression files..
From: Dmitry Moskalchuk (dm_at_[hidden])
Date: 2015-10-01 01:52:39

On 30/09/15 23:04, Dmitry Moskalchuk wrote:
> Yes, that's it! Option '-m64' is not added to b2 invocation. As I see,
> this happens due to bug in regression.py. There is following code
> (https://github.com/boostorg/regression/blob/develop/testing/src/regression.py#L282):
>
> # if no -m bjam option add -m64 (limit target to 64 kb of output)
> if self.bjam_options.find('-m') == -1:
>     self.bjam_options += ' -m64'

So I did experiment - run regression tests for ubuntu's gcc/clang with
the same bjam options we're using for Android testing. First time I ran
it with the following command:

./run.py --runner=CrystaX.NET-ubuntu14.04 --tag=develop
--toolsets=gcc-4.9,clang-3.5 --platform=Linux --bjam-options="-j16
variant=release link=static,shared runtime-link=shared threading=multi
address-model=64"

This prevent adding "-m64" to b2 invocation due to bug described above.
This make bjam.log of 2.5 GiB and XML file of the approximately the same
size.

Then I've started it with the same command line, but adding "-m64" to
bjam options:

./run.py --runner=CrystaX.NET-ubuntu14.04 --tag=develop
--toolsets=gcc-4.9,clang-3.5 --platform=Linux --bjam-options="-j16
variant=release link=static,shared runtime-link=shared threading=multi
address-model=64 -m64"

This time bjam.log was 221 MiB, and corresponding XML file 161 MiB.

So adding "-m64" option definitely fix the problem and soon all
CrystaX.NET reports will be updated with files of significantly less size.

-- 
Dmitry Moskalchuk