The emulator produces some debugging output on the Linux terminal. When running as part of a Marionette test case, this output is not shown. It would be helpful to write it to a file, etc.

Hi Jonathan, Could you find someone from the A-Team to implement this feature? I work on bug 980851, which adds (quite complex) NFC support to the emulator. When writing test cases, I often run into situations were the test case simply timeouts and it's almost impossible to figure out if the emulator or the test case is broken. Having the emulator's output would help a lot. Thanks Thomas

I spoke to :tzimmermann about this and it is not a blocker. I have set priority so that we can triage it when there is a free person to pick it up. Ahal points out that you can get logcat info from adding |--logcat-dir| to the command. 16:24 ahal: AutomatedTester: tzimmermann: currently emulator output is saved in a file called 'qemu.log' and it gets uploaded to blobber when run in tbpl 16:24 AutomatedTester: ahal: aha, thanks for that 16:25 tzimmermann: AutomatedTester: it's definately not a blocker 16:25 tzimmermann: ahal: where can i find that file locally? 16:25 AutomatedTester: tzimmermann: ok cool, will update the bug especially after ahal's comment, with what has been discussed 16:26 ahal: tzimmermann: you can pass in --logcat-dir 16:26 ahal: (it should be called --logdir I think, but it used to only be for saving logcats) 16:27 tzimmermann: ahal: but logcat is not what i'd need. i need the output of the emulator binary 16:27 ahal: tzimmermann: yes, it just piggybacks off the same command line parameter (which is confusing, and I'm in the middle of a marionette+emulator.py refactor that will make it less confusing) 16:28 ahal: tzimmermann: two logs will be saved in that directory, one is the logcat, the other is output from the emulator binary 16:28 tzimmermann: ahal: oh, great! i'll try this. thanks a lot!

That's just what I was looking for. As far as I'm concerned this bug report can be closed as INVALID.

as requested :)