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 Bugs | Assignee: | 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
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 | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/58839631>
Truitt Savell
This was imported in https://trac.webkit.org/changeset/251120/webkit
Ryosuke Niwa
More frequent on WK1 on macOS but also happens on iOS WK2.
Ryosuke Niwa
Committed r255104: <https://trac.webkit.org/changeset/255104>
Michael Catanzaro
We don't support requestIdleCallback so all these tests should be skipped.
Michael Catanzaro
(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
This seems to have resolved by now.