The android bots are a little different. Other than the summary, most* of the tests' logs can be found in the phones' logcats. These are collected at the end of the build and uploaded to google storage. You can click the 'logcat dump' link under the 'gsutil upload' step to download it.

* This is not true for the tests that are swarmed (currently content_browsertests and chrome_public_test). They have a different way of reporting the logcat that's currently broken. Assigning to jbudorick who's working on fixing that.

#2: all unswarmed suites run the test runner with -v. The two swarmed suites do not. I'm guessing that's what this is referring to rather than the logcat, which has never been dumped in the step stdio.

paulmeyer@, do you have a specific link to what you're looking at?

Here is an example:

https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/66737/steps/content_browsertests%20%28with%20patch%29%20on%20Android/logs/stdio

Notice that the summary is there, but you can't see the output from running each test.

I know that I could see that output when running the try bot ~1 week ago.

I take it you're expecting something like https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/66737/steps/content_unittests%20%28with%20patch%29/logs/stdio ?

I just realized that the specific error I mentioned doesn't show up in that link. It does here: https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/66997/steps/content_browsertests%20%28with%20patch%29%20on%20Android/logs/stdio

The "No forwarder daemon seems to be running" message is ok.

->stip for swarming+android stdio

#6: Yes.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ce14e226ffb160f8d1853ab5d9352434ddd32d2c

commit ce14e226ffb160f8d1853ab5d9352434ddd32d2c
Author: stip <stip@chromium.org>
Date: Fri May 13 02:18:30 2016

Add -v to swarmed android tests.

BUG= 610100 

Review-Url: https://codereview.chromium.org/1972373002
Cr-Commit-Position: refs/heads/master@{#393431}

[modify] https://crrev.com/ce14e226ffb160f8d1853ab5d9352434ddd32d2c/tools/mb/mb.py

Tests are dumping their output to stdio now. Marking as fixed.