Closed Bug 724183 Opened 14 years ago Closed 14 years ago

When make mochitest-robotium runs into a crashed process, show the stack in the make output without requiring `adb logcat` in a separate shell

Categories

(Testing :: General, defect)

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gkw, Unassigned)

Details

Sometimes I run `make mochitest-robotium` or `make -C <android objdir> mochitest-robotium` and this error pops up, but I'm not sure if it's an issue with Android, Fennec, or Robocop: /snip INFO | runtests.py | Running tests: start. org.mozilla.fennec_skywalker.tests.testFuzzer:INSTRUMENTATION_RESULT: shortMsg=Process crashed. INSTRUMENTATION_CODE: 0 INFO | automation.py | Application pid: 0 0 INFO SimpleTest START 1 INFO TEST-START | testFuzzer INFO | automation.py | Application ran for: 0:00:35.476291 Any way to get a more verbose output?
One way I can get more verbose output would be to run `adb logcat` in an another shell, and what I would mean here would be to have that stack appear in `make mochitest-robotium`. Will that be ideal?
Summary: make mochitest-robotium sometimes throws a shortMsg=Process crashed error → When make mochitest-robotium runs into a crashed process, show the stack in the make output without requiring `adb logcat` in a separate shell
I think this has started to work in the way I'm referring it to in comment 0.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.