<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - run-webkit-tests header output is wordy, not useful, should not write out by default"
href="https://bugs.webkit.org/show_bug.cgi?id=153950#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - run-webkit-tests header output is wordy, not useful, should not write out by default"
href="https://bugs.webkit.org/show_bug.cgi?id=153950">bug 153950</a>
from <span class="vcard"><a class="email" href="mailto:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
<pre>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").
The number of skipped tests is very relevant when running tests in one directory, I needed to know that many times. 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.
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.
Only these are the line that I personally don't see much use in, unless verbose logging is enabled:
<span class="quote">> Pixel tests disabled
> Regular timeout: 30000, slow test timeout: 150000
> Command line: /Users/darin/Build/Debug/WebKitTestRunner -</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>