7 Feb
2014
7 Feb
'14
11:57 a.m.
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 don't think that is the issue - it's not that the output is truncated - it's that there is *no output at all*. Or rather that the link for the "failure" leads to a file which did actually compile correctly.
Which is not to say the report truncation isn't an issue, for example: http://www.boost.org/development/tests/develop/developer/output/BP%20x86_64%... displays *one* warning and that's it. What on earth am I supposed to do with that? Thanks, John.