The situation in regards to this issue changed a bit:
- This bot is still mostly red but it has recent green builds too.
- The failure is still mostly due to content_browsertests but it has also failed due to other suits.
- And the actual failing tests from content_browsertests only from DumpAccessibilityTreeTest.* but also from DownloadContentTest.*, MediaCanPlayTypeTest.* and WebRtcBrowserTest.*.

dmazzoni@: as I'm not seeing much action recorded here I'm updating this issue to track these new situation. If you think this was a mistake let me know and I'll revert that and create a new one.

Also, to ease debugging and make sure the information is not lost I'm attaching to this issue:
A) the stdio output for the failing content_browsertests.
B) the logcat dump with *only* what came from the device AG860440IAG8AGC that ran the failing test (< 4MB instead of 410 MB).

Deleted: Lollipop Low-end Tester-builds-3097-steps-content_browsertests-logs-stdio-text.log 3.3 MB

Lollipop Low-end Tester-builds-3097-steps-content_browsertests-logs-stdio-text.log 3.3 MB View Download

Deleted: logcat_dumps-Lollipop Low-end Tester-3097_AG860440IAG8AGC_only.log.zip 2.7 MB

logcat_dumps-Lollipop Low-end Tester-3097_AG860440IAG8AGC_only.log.zip 2.7 MB Download

Extra note: these are in regards to failed build #3097: https://uberchromegw.corp.google.com/i/chromium.android/builders/Lollipop%20Low-end%20Tester/builds/3097

FYI: newer, different set of failures on the same bot: https://crbug.com/609905