[Tracking Requested - why for this release]: Permaorange Tier 2, so not blocking the merge, but a permafail nonetheless. https://treeherder.mozilla.org/logviewer.html#?job_id=106008959&repo=try
Hard to say without proper logs but I would assume this is due to bug 1341466. Geoff, what do you think?
I do not think this is really bug 1341466. The emulator is generally reliable > 95% of the time, so it seems unlikely that sudden emulator failure is causing a permaorange for this job. Also, I see socket timeouts in the log, rather than adb timeouts. On the other hand, of course there is a similar issue, in that the job is running > 3600 seconds because it doesn't give up and keeps encountering long-running failures. Since the job times out after 3600 seconds, there are fewer diagnostics available. :( It would be nice to see a logcat for this -- it might tell us what is happening on the device.
Ok, so I had another look at this and you are right, Geoff! The problematic test in question here is `test_return_value_on_alert`. And it has been added recently by Andreas on bug 1370850. In general we do not have any modal/tabmodal dialog test running for Fennec. But the patch added a test for tab modal dialogs which also gets run in Fennec. So this should not have been done. Whereby I still wonder why we do not have a permanent failure on Android for Nightly! Andreas, can you please disable the test? Thanks.
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/def7c269d7af Skip test_execute_script.py TestExecuteContent.test_return_value_on_alert on Android. r=ato