On Mon, Oct 29, 2012 at 6:59 PM, Dirk Pranke <dpra...@chromium.org> wrote: > If that's the case, it's a bug, and new to me.
The output was present on the results page, but it would only include the first, maybe, 60 lines or so. - Dana > > -- Dirk > > On Mon, Oct 29, 2012 at 3:42 PM, Terry Anderson <tdander...@chromium.org> > wrote: >> I was actually noticing that some of the stderr output was missing from a >> failing test, not a passing one. >> >> Terry >> >> >> On Sun, Oct 28, 2012 at 8:42 PM, Dirk Pranke <dpra...@chromium.org> wrote: >>> >>> As Balazs said, we don't save the stderr output from tests that pass. >>> So, you don't have to crash, but your tests have to at least fail. It >>> wouldn't be hard to change that somehow ... >>> >>> -- Dirk >>> >>> On Sun, Oct 28, 2012 at 4:29 PM, Terry Anderson <tdander...@chromium.org> >>> wrote: >>> > Hi webkit-dev, >>> > >>> > When I include fprintf(stderr, ...) statements in WebKit code that I >>> > expect >>> > to be executed when running a set of layout tests, the summary page of >>> > run-webkit-tests will sometimes only show a subset of these statements. >>> > However, when I add a CRASH() somewhere in the code, the "missing" >>> > stderr >>> > output will appear on the summary page. Has anyone else experienced this >>> > issue? Is there a way to force run-webkit-tests to display all stderr >>> > output >>> > without needing to force a crash at a particular point in the code? >>> > >>> > Terry >>> > >>> > _______________________________________________ >>> > webkit-dev mailing list >>> > webkit-dev@lists.webkit.org >>> > http://lists.webkit.org/mailman/listinfo/webkit-dev >>> > >> >> > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
