Bug 202950
| Summary: | REGRESSION: [ Windows ] Layout Test editing/async-clipboard/clipboard-wrapper-stays-alive.html is Timing out | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Truitt Savell <tsavell> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | webkit-bot-watchers-bugzilla, webkit-bug-importer, wenson_hsieh |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Truitt Savell
The following layout test is failing on Win10
editing/async-clipboard/clipboard-wrapper-stays-alive.html
Probable cause:
This started with build: https://build.webkit.org/builders/Apple%20Win%2010%20Debug%20(Tests)/builds/2924
Flakiness Dashboard:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=editing%2Fasync-clipboard%2Fclipboard-wrapper-stays-alive.html
Diff:
--- /home/buildbot/worker/win10-release-tests/build/layout-test-results/editing/async-clipboard/clipboard-wrapper-stays-alive-expected.txt
+++ /home/buildbot/worker/win10-release-tests/build/layout-test-results/editing/async-clipboard/clipboard-wrapper-stays-alive-actual.txt
@@ -1,10 +1,8 @@
+CONSOLE MESSAGE: line 14: Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'subframeNavigator.clipboard.foo = "bar"')
+FAIL: Timed out waiting for notifyDone to be called
Verifies that the wrapper for Navigator's Clipboard remains consistent across GC passes. This test must be run using WebKitTestRunner.
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-PASS subframeNavigator.clipboard.foo is "bar"
-PASS successfullyParsed is true
-TEST COMPLETE
-
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/56262343>
Truitt Savell
Marked this test as failing as part of: https://trac.webkit.org/changeset/251098/webkit
Wenson Hsieh
*** This bug has been marked as a duplicate of bug 202940 ***