[Webkit-unassigned] [Bug 153950] run-webkit-tests header output is wordy, not useful, should not write out by default

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=153950

--- Comment #2 from Darin Adler <darin at apple.com> ---
(In reply to comment #1)
> Some of these do answer relevant questions (like "why my expectation that I
> just added didn't work", or "what happened now, when I forgot to manually
> add the --debug option").

Questions relevant to who? I am unconvinced. I don’t see how the output answers either of those questions.

> The number of skipped tests is very relevant when running tests in one
> directory, I needed to know that many times.

Sure, but I am not running tests in one directory. We can write this out when doing any special type of test running, but not in the normal case.

> Seeing the number of parallel
> processes frequently helps me realize that I need to add or remove
> --fully-parallel when trying to reproduce an issue.

Yes but it never helps me. Is there some way we can make this clear to you in a less wordy way?

> And most of these are important when diagnosing an issue that someone has
> with the tests - it would be wasteful to request re-running them with extra
> logging enabled.

I’d like some evidence this is true. Could you cite any recent example where someone would have had to re-run? If re-running is the concern, then we should write this data into a file.

You haven’t convinced me that any of this output is helpful in the day-to-day while running tests.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160206/7c70d5ba/attachment.html>