Subject: Re: [boost] [EXTERNAL] [testing][jc-bell] Test compilation output truncated
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-02-24 16:38:05
On Monday 24 February 2014 18:39:18 Belcourt, Kenneth wrote:
> On Feb 24, 2014, at 10:51 AM, Andrey Semashev wrote:
> > Hi,
> > I'm facing the problem with the too low limit for the compiler output
> > size.
> > See here:
> > http://www.boost.org/development/tests/develop/developer/output/FBSD-64%20
> > jc-bell-boost-bin-v2-libs-log-test-attr_attribute_set-test-gcc-4-2-1-debug
> > -build-no-threading-multi.html
> > The output contains 2 warnings and part of what may be the actual error.
> > This log is not really helpful, so I have 2 questions:
> > 1. Can this limit be increased?
> Each tester can set this limit as they choose, the current testing default
> is 4 kb per target (-m4). Testers can change the default by passing -m# to
> run.py through --bjam-options.
I guess, I'm asking to increase the default then. If large output is affecting
some select testers, it is these testers who should reduce the limit, IMHO.
And 4 KiB is simply too low.
> > 2. Can I get the full output somehow?
> Passing -m0 will capture all output.
I understand this should be done by the tester, and then the tests should be
run again? I was hoping that the full output was saved somewhere on the
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk