Intermittent e10s browser
_webconsole _output _dom _elements _03 .js | A promise chain failed to handle a rejection: - at resource://gre/modules/commonjs/toolkit/loader .js -> resource://devtools/server/protocol .js:1125 - Error: Connection closed, pending reques
5 failures in the last week.
Priority: -- → P2
I couldn't get it to fail locally. I tried running with this three times (with --e10s once): ./mach mochitest devtools/client/webconsole/test/ --run-until-failure --repeat 1000 --start-at browser_webconsole_output_dom_elements_03.js --end-at browser_webconsole_output_dom_elements_03.js --run-until-failure It may be an interaction with a test in front of it. I'll have to test that later.
Whiteboard: [btpp-fix-later] → [btpp-fix-later][console-rewrite-fix]
This is super-frequent (to the point where disabling on affecting platforms is looking reasonable). Any chance we can bump the priority on it?
(In reply to Ryan VanderMeulen [:RyanVM] from comment #34) > This is super-frequent (to the point where disabling on affecting platforms > is looking reasonable). Any chance we can bump the priority on it? Hi, sorry about that - I'd be OK with disabling. We are going to convert this to a unit test as part of the console HTML conversion (specifically, https://github.com/devtools-html/gecko-dev/issues/234) and I'd rather spend time on that project than tracking down what's going on here.
Will do, thanks.
Pushed by email@example.com: https://hg.mozilla.org/integration/fx-team/rev/0f4d2ef453c8 Skip browser_webconsole_output_dom_elements_03.js on e10s due to frequent failures.
All the console tests were migrated and rewritten when we enabled the new console. If they're intermittent, new bugs were probably created.
You need to log in before you can comment on or make changes to this bug.