WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
168129
LayoutTest workers/sab/postMessage-clones.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=168129
Summary
LayoutTest workers/sab/postMessage-clones.html is a flaky failure
Ryan Haddad
Reported
2017-02-10 10:30:52 PST
LayoutTest workers/sab/postMessage-clones.html is a flaky failure
https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/r212114%20(10957)/results.html
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=workers%2Fsab%2FpostMessage-clones.html
--- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/workers/sab/postMessage-clones-expected.txt +++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/workers/sab/postMessage-clones-actual.txt @@ -3,11 +3,11 @@ On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". -PASS successfullyParsed is true - -TEST COMPLETE PASS memory[0] is 42 PASS otherMemory[0] is 0 PASS memory[0] is 42 PASS otherMemory[0] is 43 +PASS successfullyParsed is true +TEST COMPLETE +
Attachments
proposed fix
(2.47 KB, patch)
2017-02-27 20:18 PST
,
Alexey Proskuryakov
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Ryan Haddad
Comment 1
2017-02-10 10:45:42 PST
This is a new test added with
https://trac.webkit.org/changeset/212035
Filip Pizlo
Comment 2
2017-02-10 11:11:50 PST
Darn, that means I did a bad job writing the test.
Filip Pizlo
Comment 3
2017-02-10 12:36:13 PST
I think I fixed it in
https://trac.webkit.org/changeset/212132
.
Ryan Haddad
Comment 4
2017-02-15 20:56:04 PST
It appears that this test is still a flaky failure.
https://build.webkit.org/builders/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/builds/13234
Alexey Proskuryakov
Comment 5
2017-02-27 20:18:20 PST
Created
attachment 302918
[details]
proposed fix This is actually straightforward. Two issues: 1. waitUntilDone cannot be used in js-tests. This is very clear if you look at js-test-post.js. This is why expected test results look wrong, you don't want TEST COMPLETE to be printed out before the test is complete 2. Even with setTimeout, the test races with HTML parser. To avoid the race, the test could use onload instead of a zero delay timer. But that's not necessary once #1 is fixed. While at it, also updated doctype to HTML5, and migrated to js-test.js, which are both inconsequential changes.
Alexey Proskuryakov
Comment 6
2017-02-27 21:56:37 PST
Filed
bug 168961
about many more tests that mouse waiUntilDone.
WebKit Commit Bot
Comment 7
2017-02-28 13:56:31 PST
Comment on
attachment 302918
[details]
proposed fix Clearing flags on attachment: 302918 Committed
r213174
: <
http://trac.webkit.org/changeset/213174
>
WebKit Commit Bot
Comment 8
2017-02-28 13:56:35 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug