10:54:32 INFO - 207 INFO TEST-START | dom/animation/test/css-transitions/test_element-get-animation-players.html 10:54:32 INFO - -*-*- UserCustomizations (parent): document created: http://mochi.test:8888/tests/dom/animation/test/css-transitions/test_element-get-animation-players.html 10:54:32 INFO - -*-*- UserCustomizations (parent): _injectInWindow 10:54:32 INFO - -*-*- UserCustomizations (parent): principal status: 0 10:54:32 INFO - 208 INFO TEST-PASS | dom/animation/test/css-transitions/test_element-get-animation-players.html | - : Elided 2 passes or known failures. 10:54:32 INFO - 209 INFO TEST-UNEXPECTED-FAIL | dom/animation/test/css-transitions/test_element-get-animation-players.html | getAnimationPlayers for CSS Transitions - getAnimationPlayers for CSS Transitions: assert_true: CSS transitions have sensible start times expected true got false 10:54:32 INFO - 210 INFO TEST-PASS | dom/animation/test/css-transitions/test_element-get-animation-players.html | - : Elided 2 passes or known failures. 10:54:32 INFO - 211 INFO MEMORY STAT vsize after test: 762601472 10:54:32 INFO - 212 INFO MEMORY STAT vsizeMaxContiguous after test: 633143296 10:54:32 INFO - 213 INFO MEMORY STAT residentFast after test: 319995904 10:54:32 INFO - 214 INFO MEMORY STAT heapAllocated after test: 62971322 10:54:32 INFO - 215 INFO TEST-OK | dom/animation/test/css-transitions/test_element-get-animation-players.html | took 52ms 10:54:32 INFO - -*-*- UserCustomizations (parent): document created: http://mochi.test:8888/tests/SimpleTest/iframe-between-tests.html 10:54:32 INFO - -*-*- UserCustomizations (parent): _injectInWindow 10:54:32 INFO - -*-*- UserCustomizations (parent): principal status: 0 10:54:32 INFO - 216 INFO TEST-START | dom/apps/tests/test_app_addons.html

We only ever saw this twice and on Windows, and now, 2.5 months later, suddenly we see it 4 times and on Linux 64-bit. Something in that try run is suspicious (and probably shouldn't be landed) but it might give us a clue to what triggered this in the first place.

(In reply to Brian Birtles (:birtles) from comment #6) > We only ever saw this twice and on Windows, and now, 2.5 months later, > suddenly we see it 4 times and on Linux 64-bit. Something in that try run is > suspicious (and probably shouldn't be landed) but it might give us a clue to > what triggered this in the first place. You're right; those are mis-starred. That's bug 1141498 comment #8, and it never reached m-c. Please disregard comment #2 through comment #5, and sorry for the noise (and/or for the false hope of a clue about the two real failures).

Inactive; closing (see bug 1180138).