RESOLVED WORKSFORME 159689
[Yosemite Debug] LayoutTest imported/mathml-in-html5/mathml/presentation-markup/operators/mo-axis-height-1.html is flaky 
https://bugs.webkit.org/show_bug.cgi?id=159689
Summary [Yosemite Debug] LayoutTest imported/mathml-in-html5/mathml/presentation-mark...
Ryan Haddad
Reported 2016-07-12 14:45:53 PDT
LayoutTest imported/mathml-in-html5/mathml/presentation-markup/operators/mo-axis-height-1.html is flaky This test is a flaky failure on Yosemite Debug WK1/WK2 https://build.webkit.org/results/Apple%20Yosemite%20Debug%20WK2%20(Tests)/r203120%20(13408)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fmathml-in-html5%2Fmathml%2Fpresentation-markup%2Foperators%2Fmo-axis-height-1.html --- /Volumes/Data/slave/yosemite-debug-tests-wk2/build/layout-test-results/imported/mathml-in-html5/mathml/presentation-markup/operators/mo-axis-height-1-expected.txt +++ /Volumes/Data/slave/yosemite-debug-tests-wk2/build/layout-test-results/imported/mathml-in-html5/mathml/presentation-markup/operators/mo-axis-height-1-actual.txt @@ -1,5 +1,5 @@ ↨ -FAIL AxisHeight assert_approx_equals: mo: axis height expected 50 +/- 1 but got 70 +FAIL AxisHeight assert_approx_equals: mo: axis height expected 50 +/- 1 but got 5
Attachments
Add attachment proposed patch, testcase, etc.
Frédéric Wang (:fredw)
Comment 1 2016-07-14 00:36:39 PDT
I don't know what happened during the import but this test seems wrong since it expects a FAIL. Anyway, I reimported it in bug 158866 and fix one of the failure so let's see if that fixes the flakiness.
Frédéric Wang (:fredw)
Comment 2 2016-08-03 04:09:26 PDT
@Ryan: I'm not sure I understand how to read the flakiness dashboard but the test seems to have remained green after bug 159689.
Ryan Haddad
Comment 3 2016-08-03 13:12:27 PDT
(In reply to comment #2) > @Ryan: I'm not sure I understand how to read the flakiness dashboard but the > test seems to have remained green after bug 159689. Yep, seems to be alright now. Thanks for following up!
Note You need to log in before you can comment on or make changes to this bug.