09:20:48 INFO - TEST-PASS | test_interface.py TestInterfaceUnits.test_units | took 6419ms 09:20:48 INFO - TEST-START | test_refresh_firefox.py TestFirefoxRefresh.testReset 09:21:45 WARNING - Failed to gather test failure debug: Unable to locate window 09:21:45 WARNING - stacktrace: That doesn't look very good. Nothing in this area (ie profile reset) of Firefox has changed in the last while, so I expect there's an orthogonal problem that's causing us to crash or marionette to lose its way about where the window is. Not sure what to do about that, there isn't enough information in this log, but this component is almost certainly wrong so I'm moving it back to testing.
Tried to find a regressing change, but had no luck: https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=windows%20marionette&tochange=49c83f6481dc07a38385ae36f881e32d7f14ccd7&fromchange=2c7cfab5ec14e932a38008d1d26939ce2383b950 https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-searchStr=windows%20marionette&tochange=b29e907e4fbbd6dd635902722f3eaab658685e36&fromchange=4a964c3f1759fd893697e27809f1cd52af84a992
(In reply to OrangeFactor Robot from comment #2) > For more details, see: > https://brasstacks.mozilla.com/orangefactor/ > ?display=Bug&bugid=1330744&startday=2017-02-13&endday=2017-02-19&tree=all I don't see why any of those lately starred failures are related to this bug. I assume it was a mistake by the person who went through test failures.
Havent seen the issue since February, closing out.