Bug 181957 - Layout Test http/tests/misc/resource-timing-resolution.html is a flaky failure
Summary: Layout Test http/tests/misc/resource-timing-resolution.html is a flaky failure
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Jiewen Tan
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2018-01-22 14:58 PST by Ryan Haddad
Modified: 2018-12-06 11:33 PST (History)
10 users (show)

See Also:


Attachments
Patch (4.01 KB, patch)
2018-12-05 17:59 PST, Jiewen Tan
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2018-01-22 14:58:19 PST
The following layout test is flaky on release testers

http/tests/misc/resource-timing-resolution.html

Probable cause:

Unknown.

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2Fmisc%2Fresource-timing-resolution.html

--- /Volumes/Data/slave/highsierra-release-tests-wk1/build/layout-test-results/http/tests/misc/resource-timing-resolution-expected.txt
+++ /Volumes/Data/slave/highsierra-release-tests-wk1/build/layout-test-results/http/tests/misc/resource-timing-resolution-actual.txt
@@ -3,7 +3,7 @@
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
-PASS t0 !== t1 is true
+FAIL t0 !== t1 should be true. Was false.
 PASS shouldBeNearZeroOrOne < 1e-10 || Math.abs(shouldBeNearZeroOrOne - 1) < 1e-10 is true
 PASS successfullyParsed is true
Comment 1 Ryan Haddad 2018-01-22 14:59:49 PST
The earliest failure visible on the dashboard is https://trac.webkit.org/changeset/226646/webkit, but that change is unrelated.
Comment 2 Matt Lewis 2018-01-23 15:14:56 PST
Marked as flaky https://trac.webkit.org/changeset/227451/webkit
Comment 3 Ryan Haddad 2018-12-05 16:23:51 PST
This test has become very flaky after https://trac.webkit.org/changeset/238877/webkit

The diff is the same as the one above.

https://build.webkit.org/results/Apple%20Mojave%20Release%20WK1%20(Tests)/r238912%20(1467)/results.html
Comment 4 Jiewen Tan 2018-12-05 17:07:20 PST
(In reply to Ryan Haddad from comment #3)
> This test has become very flaky after
> https://trac.webkit.org/changeset/238877/webkit
> 
> The diff is the same as the one above.
> 
> https://build.webkit.org/results/Apple%20Mojave%20Release%20WK1%20(Tests)/
> r238912%20(1467)/results.html

I don’t think so. I tried to ran the test 1000 times before and after my change. It more or less reserves the same level of flakiness. Also, I don’t think there is anything my patch could affect this test case as it doesn’t have any iframes.
Comment 5 Ryan Haddad 2018-12-05 17:11:33 PST
(In reply to Jiewen Tan from comment #4)
> (In reply to Ryan Haddad from comment #3)
> > This test has become very flaky after
> > https://trac.webkit.org/changeset/238877/webkit
> > 
> > The diff is the same as the one above.
> > 
> > https://build.webkit.org/results/Apple%20Mojave%20Release%20WK1%20(Tests)/
> > r238912%20(1467)/results.html
> 
> I don’t think so. I tried to ran the test 1000 times before and after my
> change. It more or less reserves the same level of flakiness. Also, I don’t
> think there is anything my patch could affect this test case as it doesn’t
> have any iframes.

Hm, the flakiness dashboard shows a drastic increase in the number of failures starting yesterday. Even if it isn't your revision, something definitely changed.
Comment 6 Jiewen Tan 2018-12-05 17:20:00 PST
(In reply to Ryan Haddad from comment #5)
> (In reply to Jiewen Tan from comment #4)
> > (In reply to Ryan Haddad from comment #3)
> > > This test has become very flaky after
> > > https://trac.webkit.org/changeset/238877/webkit
> > > 
> > > The diff is the same as the one above.
> > > 
> > > https://build.webkit.org/results/Apple%20Mojave%20Release%20WK1%20(Tests)/
> > > r238912%20(1467)/results.html
> > 
> > I don’t think so. I tried to ran the test 1000 times before and after my
> > change. It more or less reserves the same level of flakiness. Also, I don’t
> > think there is anything my patch could affect this test case as it doesn’t
> > have any iframes.
> 
> Hm, the flakiness dashboard shows a drastic increase in the number of
> failures starting yesterday. Even if it isn't your revision, something
> definitely changed.

How about I fix the thing and relieve us all.
Comment 7 Jiewen Tan 2018-12-05 17:59:27 PST
Created attachment 356689 [details]
Patch
Comment 8 Ryan Haddad 2018-12-05 20:25:04 PST
(In reply to Jiewen Tan from comment #6)
> How about I fix the thing and relieve us all.

Works for me. Thanks, Jiewen!
Comment 9 Jiewen Tan 2018-12-06 11:06:42 PST
Comment on attachment 356689 [details]
Patch

Thanks Youenn for r+ it.
Comment 10 WebKit Commit Bot 2018-12-06 11:32:47 PST
Comment on attachment 356689 [details]
Patch

Clearing flags on attachment: 356689

Committed r238935: <https://trac.webkit.org/changeset/238935>
Comment 11 WebKit Commit Bot 2018-12-06 11:32:48 PST
All reviewed patches have been landed.  Closing bug.
Comment 12 Radar WebKit Bug Importer 2018-12-06 11:33:43 PST
<rdar://problem/46529944>