7 Feb
2014
7 Feb
'14
4:59 p.m.
On Feb 7, 2014, at 6:33 AM, Beman Dawes wrote:
On Fri, Feb 7, 2014 at 5:10 AM, John Maddock
wrote: 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.
Is that a symptom of the execution timing out?
I've noticed this before when a tester runs multiple toolsets, like Marshall's mac, the test report can be misleading or just plain wrong for some libraries. Have you seen the no output problem with single toolset runs?