Bug 206676

Summary: imported/w3c/web-platform-tests/requestidlecallback/callback-xhr-sync.html is flaky failure
Product: WebKit Reporter: Jacob Uphoff <jacob_uphoff>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: mcatanzaro, rniwa, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 164193    

Jacob Uphoff
Reported 2020-01-23 10:33:08 PST
imported/w3c/web-platform-tests/requestidlecallback/callback-xhr-sync.html is flaky failing on macOS and iOS with wk1 and wk2 I did not try to reproduce the failure History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Frequestidlecallback%2Fcallback-xhr-sync.html Diff: --- /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/requestidlecallback/callback-xhr-sync-expected.txt +++ /Volumes/Data/slave/mojave-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/requestidlecallback/callback-xhr-sync-actual.txt @@ -1,5 +1,3 @@ -Harness Error (TIMEOUT), message = null +PASS re-schedule idle callbacks after sync xhr -TIMEOUT re-schedule idle callbacks after sync xhr Test timed out -
Attachments
Radar WebKit Bug Importer
Comment 1 2020-01-23 10:33:36 PST
Truitt Savell
Comment 2 2020-01-24 08:50:14 PST
Ryosuke Niwa
Comment 3 2020-01-24 16:26:43 PST
More frequent on WK1 on macOS but also happens on iOS WK2.
Ryosuke Niwa
Comment 4 2020-01-24 16:34:12 PST
Michael Catanzaro
Comment 5 2023-03-14 14:27:48 PDT
We don't support requestIdleCallback so all these tests should be skipped.
Michael Catanzaro
Comment 6 2023-03-15 07:50:09 PDT
(In reply to Michael Catanzaro from comment #5) > We don't support requestIdleCallback so all these tests should be skipped. Sorry, this was wrong. I see now that Ryosuke had been working on this feature and imported the tests intentionally (comment #2).
Ryosuke Niwa
Comment 7 2023-08-06 02:19:10 PDT
This seems to have resolved by now.
Note You need to log in before you can comment on or make changes to this bug.