Remove misleading atest stacktrace on instrumentation crashes
When instrumentation tests crash on startup, we get mismatched events
from tradefed. Rather than try and fix this, take it as a given and
provide a clearer message to the user.
All we do is catch our raised exception and print a message rather than
a stack dump.
Some of the python files are failing the lint check with previous
problems. I'm ignoring in this cl but will fixup in a followup.
Before pic: https://screenshot.googleplex.com/Ak3P4FNW9bHkbWP
After pic: https://screenshot.googleplex.com/8ghpw554wToC4en
Fixes: b/303140004
Test: atest-dev non_starting_java_instrumentation_test
Test: atest atest_test_archetype_integration_tests
Change-Id: I372af96f9c1bcd75cd18f20bfac01d9b688ad51e
5 files changed
