Bug 207559

Summary: [ macOS iOS ] fast/parser/parser-yield-timing.html is a flaky failure
Product: WebKit Reporter: Jacob Uphoff <jacob_uphoff>
Component: Tools / TestsAssignee: Ryosuke Niwa <rniwa>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, ggaren, koivisto, rniwa, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Delete the test ggaren: review+

Jacob Uphoff
Reported 2020-02-11 09:39:17 PST
fast/parser/parser-yield-timing.html This test has been flaky failing for all visible history. Test is failing on macOS wk1 and iOS wk2 on debug. I ran the test on macOS wk1 5000 times and I was able to reproduce the failure. History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fparser%2Fparser-yield-timing.html&limit=50000 Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/fast/parser/parser-yield-timing-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/fast/parser/parser-yield-timing-actual.txt @@ -5,7 +5,7 @@ PASS new Date().getTime() - startTime is within 400 of 1000 PASS new Date().getTime() - startTime is within 400 of 2000 -PASS new Date().getTime() - startTime is within 400 of 3000 +FAIL new Date().getTime() - startTime should be within 400 of 3000. Was 3423. PASS successfullyParsed is true TEST COMPLETE
Attachments
Delete the test (6.08 KB, patch)
2020-03-23 15:38 PDT, Ryosuke Niwa 		ggaren: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-02-11 09:39:38 PST
<rdar://problem/59351383>
Ryosuke Niwa
Comment 2 2020-03-23 15:38:13 PDT
Created attachment 394313 [details] Delete the test
Geoffrey Garen
Comment 3 2020-03-23 21:37:16 PDT
Comment on attachment 394313 [details] Delete the test r=me
Ryosuke Niwa
Comment 4 2020-03-24 12:19:32 PDT
Committed r258927: <https://trac.webkit.org/changeset/258927>
Note You need to log in before you can comment on or make changes to this bug.