Bug 33372

REGRESSION(r52976): platform/mac/editing/input/devanagari-ligature.html is failing on Snow Leopard Release --- layout-test-results/platform/mac/editing/input/devanagari-ligature-expected.txt 2010-01-08 00:05:31.000000000 -0800 +++ layout-test-results/platform/mac/editing/input/devanagari-ligature-actual.txt 2010-01-08 00:05:31.000000000 -0800 @@ -4,6 +4,6 @@ RenderBlock {HTML} at (0,0) size 800x600 RenderBody {BODY} at (8,8) size 784x584 RenderBlock {DIV} at (0,0) size 784x19 - RenderText {#text} at (0,1) size 11x18 - text run at (0,1) width 11: "\x{915}\x{94D}\x{937}" + RenderText {#text} at (0,1) size 21x18 + text run at (0,1) width 21: "\x{915}\x{94D}\x{937}" caret: position 3 of child 0 {#text} of child 1 {DIV} of child 1 {BODY} of child 0 {HTML} of document I expect this is the same kind of bug as bug 32294. Unfortunately I do not have a Snow Leopard box, so I can't reproduce this. Someone else will have to find out what test was affecting platform/mac/editing/input/devanagari-ligature.html. To do so, I recommend: 1. Confirm that running platform/mac/editing/input/devanagari-ligature.html by itself "fails" (in this case, it was previously being affected by an http or websocket test and we didn't notice) in this case, the currently checked in result is incorrect, and we need to figure out which test before devanagari-ligature.html is affecting it to cause this failure. 2. Assuming it failed when run alone, check out r52975. Figure out what 1000 tests are run prior to devanagari-ligature.html. To do that: 3. run-webkit-tests -v 4. Select all tests output lines prior to and including platform/mac/editing/input/devanagari-ligature.html 5. pbpaste | awk '{ print $2 }' | tail -n 1000 > failing_set.txt will write the 1000 tests prior to (and including platform/mac/editing/input/devanagari-ligature.html) 6. cat failing_set.txt | xargs run-webkit-tests and confirm that those tests still "pass" Now to find out which test or tests is affecting devanagari-ligature.html, do: 7. Remove some tests from failing_set.txt 8. re-run cat failing_set.txt | xargs run-webkit-tests 9. if run-webkit-tests exits non-zero ("fails") then we've removed too many, go back to step 7 remove different tests, otherwise remove more tests until you can't remove any more. Tada! At least that's the methodology I used to figure out bug 32294, which again, I believe to be a similar cause.