Open Bug 1455996 Opened 2 years ago Updated 18 days ago

Intermittent docshell/test/iframesandbox/test_marquee_event_handlers.html | Test timed out.

Categories

(Core :: DOM: Security, defect, P5)

defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned, NeedInfo)

Details

(Keywords: intermittent-failure, leave-open, test-disabled, Whiteboard: [domsecurity-intermittent])

Attachments

(2 files)

Filed by: ncsoregi [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=175038440&repo=autoland

https://queue.taskcluster.net/v1/task/AtXBLUZDSVOolFevZaUQEw/runs/0/artifacts/public/logs/live_backing.log

20:18:07     INFO -  165 INFO TEST-START | docshell/test/iframesandbox/test_marquee_event_handlers.html
20:23:36     INFO -  TEST-INFO | started process screenshot
20:23:36     INFO -  TEST-INFO | screenshot: exit 0
20:23:36     INFO -  Buffered messages logged at 20:18:07
20:23:36     INFO -  166 INFO if1 event finish fired
20:23:36     INFO -  167 INFO if2 marquee onstart message received
20:23:36     INFO -  168 INFO if2 marquee onbounce message received
20:23:36     INFO -  169 INFO if2 marquee onfinish message received
20:23:36     INFO -  Buffered messages finished
20:23:36    ERROR -  170 INFO TEST-UNEXPECTED-FAIL | docshell/test/iframesandbox/test_marquee_event_handlers.html | Test timed out.
20:23:36     INFO -      reportError@SimpleTest/TestRunner.js:121:7
20:23:36     INFO -      TestRunner._checkForHangs@SimpleTest/TestRunner.js:142:7
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5
20:23:36     INFO -      TestRunner.runTests@SimpleTest/TestRunner.js:380:5
20:23:36     INFO -      RunSet.runtests@SimpleTest/setup.js:194:3
20:23:36     INFO -      RunSet.runall@SimpleTest/setup.js:173:5
20:23:36     INFO -      hookupTests@SimpleTest/setup.js:266:5
20:23:36     INFO -  parseTestManifest@http://mochi.test:8888/manifestLibrary.js:36:5
20:23:36     INFO -  getTestManifest/req.onload@http://mochi.test:8888/manifestLibrary.js:49:11
20:23:36     INFO -  EventHandlerNonNull*getTestManifest@http://mochi.test:8888/manifestLibrary.js:45:3
20:23:36     INFO -      hookup@SimpleTest/setup.js:246:5
20:23:36     INFO -  EventHandlerNonNull*@http://mochi.test:8888/tests?autorun=1&closeWhenDone=1&consoleLevel=INFO&manifestFile=tests.json&dumpOutputDirectory=c%3A%5Cusers%5Ctask_1524426588%5Cappdata%5Clocal%5Ctemp&cleanupCrashes=true:11:1
20:23:37     INFO -  GECKO(5000) | MEMORY STAT | vsize 2098554MB | vsizeMaxContiguous 129742377MB | residentFast 80MB | heapAllocated 12MB
20:23:37     INFO -  171 INFO TEST-OK | docshell/test/iframesandbox/test_marquee_event_handlers.html | took 329795ms
Whiteboard: [domsecurity-intermittent]

This test fails intermitently on many test platforms, but mostly on android-em-7-0-x86_64
(geckoview); I'd like to skip it there as I'm trying to get those jobs passing more
reliably.

Looks like this is a race between the setup of the event handler from the parent and the start event.
I have an idea to make this reliable, I'll try and look at it soon.

Flags: needinfo?(bobowencode)
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/31e2f80bc00d
Skip test_marquee_event_handlers.html on geckoview for intermittent failures; r=bobowen

There seems to be a spike of failures in the last 7 days, 42 to be more precise: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-06-26&endday=2019-07-03&tree=trunk&bug=1455996

Affected platforms are windows7-32-shippable, windows7-32, windows10-64-shippable-qr, windows10-64-shippable, windows10-64 debug, macosx1014-64 debug, macosx1010-64-shippable opt, macosx1010-64 debug, linux64-shippable-qr and linux64

Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=254563213&repo=autoland&lineNumber=2856

09:13:28 INFO - TEST-START | docshell/test/iframesandbox/test_marquee_event_handlers.html
09:18:57 INFO - TEST-INFO | started process screenshot
09:18:57 INFO - TEST-INFO | screenshot: exit 0
09:18:57 INFO - Buffered messages logged at 09:13:28
09:18:57 INFO - if1 event finish fired
09:18:57 INFO - if2 marquee onstart message received
09:18:57 INFO - if2 marquee onbounce message received
09:18:57 INFO - if2 marquee onfinish message received
09:18:57 INFO - Buffered messages finished
09:18:57 INFO - TEST-UNEXPECTED-FAIL | docshell/test/iframesandbox/test_marquee_event_handlers.html | Test timed out.
09:18:57 INFO - SimpleTest.ok@SimpleTest/SimpleTest.js:275:18
09:18:57 INFO - reportError@SimpleTest/TestRunner.js:121:22
09:18:57 INFO - TestRunner._checkForHangs@SimpleTest/TestRunner.js:142:7
09:18:57 INFO - setTimeout handler*TestRunner._checkForHangs@SimpleTest/TestRunner.js:163:5

Geoff, can you please take a look at it?

Flags: needinfo?(gbrown)

Failures are affecting all platforms now. Let's skip the test entirely until
you can make it more reliable.

Flags: needinfo?(gbrown)
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a030c27bb1c1
Skip mochitest test_marquee_event_handlers.html; r=bobowen
You need to log in before you can comment on or make changes to this bug.