Alexandre, do you have cycles to look into this new failure?
This test also had bug 1328192 filed against it recently, so that might be related.
I'm not able to reproduce it locally. That doesn't help. I see two exceptions: task 2017-01-07T00:43:15.424118Z] 00:43:15 INFO - console.error: [task 2017-01-07T00:43:15.432470Z] 00:43:15 INFO - Message: Error: Connection closed, pending request to server1.conn0.child1/performanceActor22, type connect failed Which sounds like a cross test mixup. Given the stacks, it seems to break the test and introduce this second exception: [task 2017-01-07T00:43:15.588618Z] 00:43:15 INFO - Full message: TypeError: editor is null [task 2017-01-07T00:43:15.589450Z] 00:43:15 INFO - Full stack: waitForEditorEvents@chrome://mochitests/content/browser/devtools/client/debugger/test/mochitest/head.js:396:3 It looks like the connection opened for this test is closed while the test starts. I'm wondering if it is related to the same race we have in bug 1328004 and bug 1319928. But this intermittent should have appeared sooner during december. Or may be there wasn't enough activity??
Looks like it is not bug 1328004, as the following push to try with a tentative fix still fails: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f3b0e847c7b82f176762fcd1188c1b9efb557b5d&selectedJob=67688753 If you have any guess of recent landing that would regress this test, that may help.
It looks like this intermittent has been fixed between 9th and 11th. I had bug 1328004 in mind, but it only landed on 12th. bug 1324565 landed in this good timeframe but it has nothing to do, it just makes the toolbox faster to load on the inspector. If that's the bug which fixed this intermittent it means it will start to fail again if the inspector performances regress again.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Whiteboard: [stockwell fixed]
status-firefox52: --- → unaffected
status-firefox53: --- → fixed
status-firefox54: --- → fixed
You need to log in before you can comment on or make changes to this bug.