1355673 - Don't dump logcat at end of mochitests and reftests in automation

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: Testing, enhancement)

Description

[Geoff Brown [:gbrown]]

It clutters the test log. The logcat artifact provides much more complete information.

(Consider dumping it if a test failed.)

Comment 1

[Geoff Brown [:gbrown]]

I think the logcat should be dumped to the test log after a failed run. In the case of a MOZ_CRASH or an assertion count mismatch, the important message is in the logcat, and if that is in the test log, there's a better chance of it being noticed, copied to a bug, and acted upon.

Comment 2

[Geoff Brown [:gbrown]]

Attachment: don't dump logcat to test log on success

Just trying to clean up the logs a bit...

https://treeherder.mozilla.org/#/jobs?repo=try&revision=b81b511428046a47dc3f8b500f69b6b2a76e9e44

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

Comment on attachment 8857615 [details] [diff] [review]
don't dump logcat to test log on success

Review of attachment 8857615 [details] [diff] [review]:
-----------------------------------------------------------------

yay for simpler data!

Comment 4

[Geoff Brown [:gbrown]]

Looking at this more closely, I don't see a good way to guarantee that the logcat continues to appear in the test log for cases such as those noted in comment 1. I don't think it's worth spending more time on, so I'm not going to check this in.