Bug 207060

Summary: [ Mojave wk2 Release ] imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval.html flaky failure
Product: WebKit Reporter: Jason Lawrence <Lawrence.j>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, darin, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Update Test Expectations none

Description Jason Lawrence 2020-01-31 11:20:00 PST 
imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval.html

Description:
This test is lightly flaky failing on Mojave wk2 release.

History:
https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fhtml%2Fwebappapis%2Ftimers%2Ftype-long-setinterval.html&limit=50000&platform=mac

Diff:
--- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval-expected.txt
+++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval-actual.txt
@@ -1,3 +1,4 @@
+CONSOLE MESSAGE: line 3463: Error: assert_unreached: Reached unreachable code
 
 PASS Type long timeout for setInterval
Comment 1 Radar WebKit Bug Importer 2020-01-31 11:20:24 PST 
<rdar://problem/59068308>
Comment 2 Jason Lawrence 2020-01-31 11:37:33 PST 
Created attachment 389386 [details]
Update Test Expectations
Comment 3 Truitt Savell 2020-01-31 11:41:28 PST 
Comment on attachment 389386 [details]
Update Test Expectations

Clearing flags on attachment: 389386

Committed r255514: <https://trac.webkit.org/changeset/255514>
Comment 4 Alexey Proskuryakov 2020-02-01 17:57:03 PST 
> interval = setInterval(next, Math.pow(2, 32));
> setTimeout(assert_unreached, 100);

I think that this tests a zero delay interval vs. a 100 ms delay timeout. Are these supposed to be on the same timeline?
Comment 5 Alexey Proskuryakov 2020-02-01 18:11:45 PST 
I guess clamping makes it test something different from what the author intended, but flakiness still seems surprising to me.
Comment 6 Darin Adler 2020-02-01 18:16:44 PST 
(In reply to Alexey Proskuryakov from comment #4)
> > interval = setInterval(next, Math.pow(2, 32));
> > setTimeout(assert_unreached, 100);
> 
> I think that this tests a zero delay interval vs. a 100 ms delay timeout.
> Are these supposed to be on the same timeline?

Yes, setInterval and setTimeout should be on the same timeline.
Comment 7 Ryan Haddad 2020-05-07 15:26:29 PDT 

*** This bug has been marked as a duplicate of bug 172052 ***