1391369 - perma failing devtools/client/debugger/test/mochitest/browser_dbg_stack-[03-07].js on windows7-debug when run in non-e10s mode

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

we are turning on non-e10s tests to ensure we have full coverage on all code paths.

We turned the non-e10s tests off 2 weeks ago, and now are looking to turn them on for windows7-debug only (unless there are other needs).

here is a try push showing the failing dt8 job:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=01724ecb482db9bad166e86cf46ce32edbccb483&selectedJob=123699440&filter-searchStr=dt8

and a specific log file:
https://queue.taskcluster.net/v1/task/dpe3zPDkRS6f04cPsDjqQQ/runs/0/artifacts/public/logs/live_backing.log

here is some lines from the log file:
22:13:54     INFO -  397 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | The correct caret position has been set. -
22:13:54     INFO -  398 INFO Debugger event 'Debugger:EditorSourceShown' fired: 1 time(s).
22:13:54     INFO -  399 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Enough 'Debugger:EditorSourceShown' panel events have been fired. -
22:13:54     INFO -  400 INFO Waiting for debugger event: 'Debugger:AfterFramesRefilled' to fire: 1 time(s).
22:13:54     INFO -  401 INFO Debugger event 'Debugger:AfterFramesRefilled' fired: 1 time(s).
22:13:54     INFO -  402 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Enough 'Debugger:AfterFramesRefilled' panel events have been fired. -
22:13:54     INFO -  403 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Should only be getting stack frames while paused. -
22:13:54     INFO -  404 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Should have only the max limit of frames. -
22:13:54     INFO -  405 INFO TEST-PASS | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Should have only the max limit of frames in the mirrored view as well. -
22:13:54     INFO -  406 INFO Waiting for debugger event: 'Debugger:AfterFramesRefilled' to fire: 1 time(s).
22:13:54     INFO -  Buffered messages finished
22:13:54    ERROR -  407 INFO TEST-UNEXPECTED-FAIL | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | Test timed out -
22:13:54     INFO -  GECKO(2116) | --DOCSHELL 17FE3C00 == 9 [pid = 2116] [id = {6c502b68-8f6a-425f-b21f-043b5c6b19d6}]
22:13:54     INFO -  GECKO(2116) | ++DOMWINDOW == 22 (119A9800) [pid = 2116] [serial = 1112] [outer = 119B4000]
22:13:54     INFO -  GECKO(2116) | --DOCSHELL 1026C800 == 8 [pid = 2116] [id = {a983e791-6068-4942-b5d3-0bbd95858122}]
22:13:54     INFO -  Not taking screenshot here: see the one that was previously logged
22:13:54    ERROR -  408 INFO TEST-UNEXPECTED-FAIL | devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js | uncaught exception - TypeError: frames.widget._list.scrollByIndex is not a function at test/</</framesScrollingInterval<@chrome://mochitests/content/browser/devtools/client/debugger/test/mochitest/browser_dbg_stack-03.js:28:9


As I want to get coverage, I am going to disable for !e10s the 5 test cases

Comment 1

[Jason Laster [:jlast]]

closing as it is an old debugger test.