<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - LayoutTest performance-api/performance-now-api.html is a flaky failure"
href="https://bugs.webkit.org/show_bug.cgi?id=168066#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - LayoutTest performance-api/performance-now-api.html is a flaky failure"
href="https://bugs.webkit.org/show_bug.cgi?id=168066">bug 168066</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>I don't know how to make an end to end layout test that expects something to happen in a given time frame, kernel scheduling can easily make a thread stop for several seconds.
Injecting test specific code can of course work, but then it's always a question of whether the behavior is likely to be broken in a way that bypasses the test.
I think that the best question to ask with regards to a new regression test is whether it tests for something that's likely to break. The easiest way to answer it is by adding tests together with fixes - that way you know that it's fragile code, and you can confirm whether your test catches that specific failure mode.</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>