/workers/opaque-origin.html is disabled/flaky in chromium webkit #11188
Assignees
Labels
Comments
|
As mentioned on the pull request it seems the issue is that fetch_tests_from_worker used to auto-start the port (because it assigned to onmessage), and that later was changed to addEventListener('message', ...) instead. So presumably that could effect more than just this test (unless there is special code already to make sure a shared worker's port is started for example)? |
zcorpan
added a commit
that referenced
this issue
May 30, 2018
|
Test enabled in https://chromium-review.googlesource.com/1140053. |
aarongable
pushed a commit
to chromium/chromium
that referenced
this issue
Jul 17, 2018
There haven't been any crashes or timeouts in a long time, only normal failures: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=%2Fworkers%2Fopaque-origin.html See web-platform-tests/wpt#11188. Change-Id: I933124b8c406fd202a7d382350cfe259d6607d79 Reviewed-on: https://chromium-review.googlesource.com/1140053 Commit-Queue: Robert Ma <robertma@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#575647}
|
Filed https://bugs.webkit.org/show_bug.cgi?id=197705 to get the test enabled in WebKit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http://bocoup.github.io/wpt-disabled-tests-report/
Investigate what's up with this test:
cc @mkruisselbrink
I think the issue is that the test isn't enabling the port message queue, it needs
channel.port1.start();The text was updated successfully, but these errors were encountered: