RESOLVED FIXED 86786
mathml/presentation/mo-stretch.html and mroot-pref-width.html tests fail on Mac
https://bugs.webkit.org/show_bug.cgi?id=86786
Summary mathml/presentation/mo-stretch.html and mroot-pref-width.html tests fail on Mac
Brady Eidson
Reported 2012-05-17 16:20:21 PDT
Two mathml/presentation tests fail on Mac. mathml/presentation/mo-stretch.html mathml/presentation/mroot-pref-width.html http://build.webkit.org/results/Lion%20Debug%20(Tests)/r117482%20(6690)/results.html includes an example of the failures. Due to gaps in testing coverage, it's unclear when these failures were introduced. They started failing sometime between 117198 and 117355
Attachments
Patch (94.24 KB, patch)
2012-05-25 12:22 PDT, Dave Barton
darin: review+
Brady Eidson
Comment 1 2012-05-17 16:25:44 PDT
Radar WebKit Bug Importer
Comment 2 2012-05-17 16:28:16 PDT
Dave Barton
Comment 3 2012-05-18 16:36:49 PDT
It looks like it may be from r117339. That patch is relevant (tables), and seems to have caused a lot of rebaselining - see http://trac.webkit.org/search?q=117339 I will look at this after my current patch, if no one else does.
Dave Barton
Comment 4 2012-05-25 10:44:07 PDT
The two mathml tests that r117339 made fail actually are: mathml/presentation/row-alignment.xhtml mathml/presentation/tables.xhtml These are already in LayoutTests/platform/mac-lion/Skipped, along with all the other mathml pixel tests, except the two you're skipping here. Your two (mo-stretch.html and mroot-pref-width.html) are newer tests that I added fairly recently, which is why they weren't already skipped. I have a fix for row-alignment.xhtml and tables.xhtml that I will submit shortly. I would also like to get all these tests passing, or find out why not. The mathml tests do all pass for me on Snow Leopard. The link you give showing your failures is now broken, and I'm running on Snow Leopard, so I can't verify things on Lion. What is the best way for me to proceed? Should I attach a patch that removes some Skipped lines, and see what the Lion bot(s) do with these tests now? Will I be able to see and/or download the output on Lion so I can troubleshoot it when necessary? Sorry, I am fairly new to WebKit (just made a committer). Thanks in advance for any suggestions or instructions.
Dave Barton
Comment 5 2012-05-25 12:22:47 PDT
Dave Barton
Comment 6 2012-05-25 12:24:42 PDT
r117339 actually also made mo-stretch.html fail, but I don't know about mroot-pref-width.html. I've uploaded a patch to hopefully see.
Dave Barton
Comment 7 2012-05-25 14:33:12 PDT
Thanks for the review+! Is there a way to test this patch on e.g. the Lion Debug (Tests) bot other than committing it? I've yet to land my first patch, let alone back one out, so I'm looking for some guidance or help here, thanks!
Julien Chaffraix
Comment 8 2012-05-25 17:41:28 PDT
(In reply to comment #7) > Thanks for the review+! Is there a way to test this patch on e.g. the Lion Debug (Tests) bot other than committing it? I've yet to land my first patch, let alone back one out, so I'm looking for some guidance or help here, thanks! No, only the Chromium Linux EWS runs the tests at the moment so your only choice is to commit the patch and see what happens. You can always preemptively disable the tests that you know will require some new baseline to avoid turning the bots red. Also it's better to be on IRC around the time you land to coordinate with the gardener / bot watcher.
Dave Barton
Comment 9 2012-05-28 18:24:50 PDT
Dave Barton
Comment 10 2012-05-28 20:17:14 PDT
Thanks Julien for all the info. I landed the patch, and mo-stretch.html failed, so I then re-skipped these two tests pending further investigation. Manually committed r118717: http://trac.webkit.org/changeset/118717
Dave Barton
Comment 11 2012-05-30 10:25:32 PDT
Dave Barton
Comment 12 2012-05-30 10:52:02 PDT
Manually committed r118939: http://trac.webkit.org/changeset/118939 I am rebaselining and unskipping mathml tests. My understanding is this doesn't need to be reviewed, but if I'm wrong please let me know, thanks!
Note You need to log in before you can comment on or make changes to this bug.