<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Modern IDB: Test flakes and failures umbrella"
href="https://bugs.webkit.org/show_bug.cgi?id=154968#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Modern IDB: Test flakes and failures umbrella"
href="https://bugs.webkit.org/show_bug.cgi?id=154968">bug 154968</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154968#c3">comment #3</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=154968#c2">comment #2</a>)
> > Primary strategy going forward for diagnosing these is to gather IndexedDB
> > logs during the test and to dump them in case the test times out.
> >
> > This is tracked by <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Add the ability to accumulate logs for specific logging channels to help diagnose test timeouts"
href="show_bug.cgi?id=157274">https://bugs.webkit.org/show_bug.cgi?id=157274</a>
>
> As of <a href="http://trac.webkit.org/changeset/200346">http://trac.webkit.org/changeset/200346</a> we now have this logging
> mechanism in place for WK1 timeouts.
>
> WK2 will be a bit more tricky.</span >
The WK1 functionality should (eventually) get us useful information for 5 of these known flakes.</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>