Intermittent Tier 2 dom/plugins/test/mochitest/test_bug1028200-4.html | expected-crash-dump-missing - This test did not leave any crash dumps behind, but we were expecting some! | Finished in 850ms
Categories
(Core Graveyard :: Plug-ins, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure, regression)
Filed by: btara [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=266833807&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/Cz4rxdq4THOzH_tbP-sRbQ/runs/0/artifacts/public/logs/live_backing.log
11:25:26 INFO - TEST-START | dom/plugins/test/mochitest/test_bug1028200-4.html
11:25:26 INFO - GECKO(2648) | ###!!! [Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
11:25:26 INFO - GECKO(2648) | ###!!! [Parent][MessageChannel] Error: (msgtype=0x6C001E,name=PPluginInstance::Msg_AsyncSetWindow) Channel error: cannot send/recv
11:25:27 INFO - GECKO(2648) | MEMORY STAT | vsize 6701MB | vsizeMaxContiguous 68131419MB | residentFast 112MB | heapAllocated 14MB
11:25:27 INFO - Buffered messages logged at 11:25:26
11:25:27 INFO - TEST-PASS | dom/plugins/test/mochitest/test_bug1028200-4.html | A valid string reason is expected
11:25:27 INFO - TEST-PASS | dom/plugins/test/mochitest/test_bug1028200-4.html | Reason cannot be empty
11:25:27 INFO - add_task | Entering test
11:25:27 INFO - add_task | Leaving test
11:25:27 INFO - add_task | Entering test
11:25:27 INFO - TEST-PASS | dom/plugins/test/mochitest/test_bug1028200-4.html | Element is fullscreen
11:25:27 INFO - TEST-PASS | dom/plugins/test/mochitest/test_bug1028200-4.html | Plugin was crashed
11:25:27 INFO - add_task | Leaving test
11:25:27 INFO - add_task | Entering test
11:25:27 INFO - TEST-FAIL | dom/plugins/test/mochitest/test_bug1028200-4.html | The author of the test has indicated that flaky timeouts are expected. Reason: This is needed in the event the fullscreen element fails to cancel fullscreen. The fullscreen element is expected to exit fullscreen but takes some time to register as having exited when using mozCancelFullScreen. So we can't just check that mozFullScreenElement is true or false after having called mozCancelFullScreen without the timeout because it will return the value prior to actually cancelling. A timeout is preferred here as opposed to polling methods similar to SimpleTest.waitForCondition in SimpleTest.js for reasons ofidiomaticity.
11:25:27 INFO - TEST-PASS | dom/plugins/test/mochitest/test_bug1028200-4.html | Element is no longer fullscreen
11:25:27 INFO - add_task | Leaving test
11:25:27 INFO - Buffered messages finished
11:25:27 INFO - TEST-UNEXPECTED-ERROR | dom/plugins/test/mochitest/test_bug1028200-4.html | expected-crash-dump-missing - This test did not leave any crash dumps behind, but we were expecting some!
11:25:27 INFO - TEST-UNEXPECTED-ERROR | dom/plugins/test/mochitest/test_bug1028200-4.html | Finished in 850ms
11:25:27 INFO - {u'runtime': 850}
11:25:27 INFO - TEST-INFO took 850ms
| Comment hidden (Intermittent Failures Robot) |
|
||
Comment 2•6 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.
| Comment hidden (Intermittent Failures Robot) |
|
||
Updated•4 years ago
|
Description
•