RESOLVED FIXED 94327
[EFL] Change font family/script on layout tests causes flakiness
https://bugs.webkit.org/show_bug.cgi?id=94327
Summary [EFL] Change font family/script on layout tests causes flakiness
Thiago Marcos P. Santos
Reported 2012-08-17 03:43:56 PDT
Many tests are flaky on the WK1 bot because changing the font family/script doesn't get properly reset by DRT. This should pass: ./Tools/Scripts/run-webkit-tests --efl --debug --child-processes=1 ietestcenter/css3/bordersbackgrounds/background-attachment-local-scrolling.htm This should also pass: ./Tools/Scripts/run-webkit-tests --efl --debug --child-processes=1 fast/text/international/font-fallback-to-common-script.html Running both tests sequentially reveals flakiness: ./Tools/Scripts/run-webkit-tests --efl --debug --child-processes=1 fast/text/international/font-fallback-to-common-script.html ietestcenter/css3/bordersbackgrounds/background-attachment-local-scrolling.htm
Attachments
Patch (3.51 KB, patch)
2012-08-17 04:58 PDT, Thiago Marcos P. Santos
no flags
Thiago Marcos P. Santos
Comment 1 2012-08-17 04:58:37 PDT
Kenneth Rohde Christiansen
Comment 2 2012-08-17 05:16:51 PDT
Comment on attachment 159089 [details] Patch It is possible to write a test which always fails without this change?
Chris Dumez
Comment 3 2012-08-17 05:19:47 PDT
Comment on attachment 159089 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=159089&action=review > Source/WebKit/efl/ewk/ewk_view.cpp:2505 > + eina_stringshare_replace(&priv->settings.fontStandard, name); I would have added a comment in the code to explain why it is needed to call setStandardFontFamily() even if the font family has not changed. This would make sure someone does not break this when refactoring.
WebKit Review Bot
Comment 4 2012-08-17 05:23:36 PDT
Comment on attachment 159089 [details] Patch Clearing flags on attachment: 159089 Committed r125885: <http://trac.webkit.org/changeset/125885>
WebKit Review Bot
Comment 5 2012-08-17 05:23:42 PDT
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.