Filed by: rvandermeulen [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=93851803&repo=mozilla-beta https://autophone.s3.amazonaws.com/v1/task/AkTutF4rTZ6XDDCw40zxiw/runs/1/artifacts/public/build/robocoptest-autophone-robocoptests-autophone-settings.ini-1-nexus-5-2-e0903d21-4f82-4bf0-9f22-00a59459027e.log
Seeing this on Beta and Release now. Not enough new results on trunk to say whether it's happening or not there yet.
status-firefox53: --- → affected
status-firefox55: --- → ?
status-firefox-esr52: --- → unaffected
This might be device related. So far this is happening on nexus-5-2 debug builds only. Van checked this device earlier today and perhaps changed something. Van, any idea why this device thinks its display is off?
5-2 should be good now.
7 failures in 883 pushes (0.008 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * mozilla-beta: 4 * mozilla-central: 2 * mozilla-release: 1 Platform breakdown: * android-4-4-armv7-api15: 7 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1359236&startday=2017-04-24&endday=2017-04-30&tree=all
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.