WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
71653
[Chromium] Layout Test platform/chromium-cg-mac/editing/input/ime-candidate-window-position.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=71653
Summary
[Chromium] Layout Test platform/chromium-cg-mac/editing/input/ime-candidate-w...
Yuta Kitamura
Reported
2011-11-07 00:00:48 PST
The following layout test is flaky (pass / timeout) on all platforms. platform/chromium-cg-mac/editing/input/ime-candidate-window-position.html See
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=platform%2Fchromium-cg-mac%2Fediting%2Finput%2Fime-candidate-window-position.html
Probable cause: Unknown, as it's not clear when this flakiness started. This test is less flaky on DEPS bots.
Attachments
Patch
(2.17 KB, patch)
2011-11-07 20:58 PST
,
Kenichi Ishibashi
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Kenichi Ishibashi
Comment 1
2011-11-07 01:18:24 PST
Umm, I don't have any idea. Maybe recent editing changes trigger this flaky?
Ryosuke Niwa
Comment 2
2011-11-07 09:03:26 PST
My suspicion is that doTest() is called before iframe is loaded, and doTest is encountering some javascript error and end up not calling finishJSTest. We should probably move finishJSTest above if with setTimeout(~, 0) so that we can see the diff.
Kenichi Ishibashi
Comment 3
2011-11-07 20:58:02 PST
Created
attachment 113983
[details]
Patch
Kenichi Ishibashi
Comment 4
2011-11-07 21:00:16 PST
(In reply to
comment #2
)
> My suspicion is that doTest() is called before iframe is loaded, and doTest is encountering some javascript error and end up not calling finishJSTest. > > We should probably move finishJSTest above if with setTimeout(~, 0) so that we can see the diff.
It seems you are right. I changed the test to call doTest() after iframe is loaded and iterated layout test 10 times, but no timeout occurred.
Kent Tamura
Comment 5
2011-11-07 21:03:01 PST
Comment on
attachment 113983
[details]
Patch ok, let's land this and watch the dashboard.
Ryosuke Niwa
Comment 6
2011-11-07 21:03:48 PST
(In reply to
comment #4
)
> It seems you are right. I changed the test to call doTest() after iframe is loaded and iterated layout test 10 times, but no timeout occurred.
Could you reproduce the issue (intermittent failure) without your patch? It's still odd that load event is fired before the iframe is loaded though. HTML5 spec is explicit about delaying load event until the iframe's content is loaded. Adam, do you know anything about this?
WebKit Review Bot
Comment 7
2011-11-07 22:50:09 PST
Comment on
attachment 113983
[details]
Patch Clearing flags on attachment: 113983 Committed
r99524
: <
http://trac.webkit.org/changeset/99524
>
WebKit Review Bot
Comment 8
2011-11-07 22:50:13 PST
All reviewed patches have been landed. Closing bug.
Kent Tamura
Comment 9
2011-11-08 01:27:16 PST
(In reply to
comment #7
)
> Committed
r99524
: <
http://trac.webkit.org/changeset/99524
>
It seems this didn't fix the issue.
Ryosuke Niwa
Comment 10
2011-11-08 01:33:55 PST
Hm...
http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-cg-mac/editing/resources/ime-candidate-window-position-iframe.html
and
http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-cg-mac/editing/input/ime-candidate-window-position.html#L27
both try to focus the same node. So maybe there's some race condition there? Also, can we do setTimeout(finishJSTest, 0) before if statement so that we can at least see the diff if the test were to fail?
Stephen Chenney
Comment 11
2013-04-09 16:28:24 PDT
Marking test failures as WontFix. Bug is still accessible and recording in TestExpectations.
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