Re: [boost] [EXTERNAL] [testing] More failed test results with no meaningful content

Subject: Re: [boost] [EXTERNAL] [testing] More failed test results with no meaningful content
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-02-06 14:50:05

On Thursday 06 February 2014 19:33:11 Belcourt, Kenneth wrote:
> On Feb 6, 2014, at 12:22 PM, John Maddock wrote:
> > For example:
> > http://www.boost.org/development/tests/develop/developer/output/marshall-> > mac-boost-bin-v2-libs-math-test-test_igamma_inva_float-test-clang-darwin-t
> > ot-debug-link-static.html leads to a successfully compiled file if you
> > follow the links.
> > 
> > Anyone any idea what's going on here, and is there any way to make this
> > reporting more reliable?  Frankly the results will get widely ignored if
> > no one can see what's actually going on.
> We made a recent change to limit how much output is captured from test
> targets to 4k per target.  We can bump this up though it may adversely
> impact some testers who have more limited bandwidth.  How about 16k per
> target and let us know if that's still insufficient?

I have a similar problem with the output that only shows the library target:

http://www.boost.org/development/tests/master/developer/marshall-mac-log-clang-darwin-asan-attr_attribute_set-variants_.html

Is it still considered "the test target"? I don't see a note that says that 
the output is truncated due to size limits. Is it supposed to be still 
appended?

4k sounds extremely small, and 16k too, BTW. It was 64k before, IIRC, and I 
did see the note about truncated output from time to time. Some compiler 
errors may easily produce 100k+ of output and I wouldn't want to lose any of 
it since there may be useful information in it.

Is bandwidth really the problem? Can't we just compress the output in scripts 
before uploading? The text should be quite well compressible.