In bug 803254 we added the ability to detect an emulator crash. But e.g in bug 811167 we are still seeing the first test crash, followed by error messages for every other test in the manifest. We should be abort the test run if we detect a crash has occurred.
(The additional failures make it quite a lot harder to quickly grok what has failed when sheriffing and dealing with multiple failures across various testsuites/platforms/trees etc)
I believe this happens because the fix in bug 803254 was developed for Python 2.7, and B2G tests are still being run with 2.6. I'm going to file a bug to get this changed, since I think Python 2.7 is available on all the test slaves.
Closing as emulator tests are no longer run because of bug 1149887
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.