After https://codereview.chromium.org/2767833002 the logcats from Android test runs are uploaded to logdog storage (which is great!). Unfortunately the link to this location is only secretly printed in the test execution log, like this:
I 246.052s Main Opening text logdog stream, unified_logcats
I 246.052s Main Getting logdog client.
C 246.069s Main Logcat: https://luci-logdog.appspot.com/v/?s=chromium%2Fandroid%2Fswarming%2Flogcats%2F35e04d2c1ccb6211%2F%2B%2Funified_logcats
It also looks weird to me that it's printed with the CRITICAL severity level, implying that this is some kind of fatal error happening.
This link should be easily accessible in the Buildbot Web UI, preferably along with all the other links presented for a test build, e.g.
stdout
swarming.summary
step_metadata
shard #0 isolated out
shard #0
From an example build: https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/168725
Having it buried in the log hides it from the average engineer, and it's inefficient to have to dig into the swarning output log to find this link when you want to view the logcat. Can we please fix this?
I'm setting this as Bug-Regression type, since such links were present in the past (pre-swarming days) as a separate build step.
Bonus: It would also be useful to write a logcat.log into the "isolated outputs" folder, since that's a location one would expect such a file to end up.
Thanks for progress here. I see logcats are produced in the isolated output dir now, which is great. Will it be possible to also get a link to the logcat file in Web UI as well? I think that would be highly appreciated by developers.
I'm also trying to figure out why we don't see the logcats file in isolated output for our WebRTC bots. Are you able to see what we're missing? We're using the same chromium_tests.steps.GTestTest class as the other recipes here: https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/webrtc/steps.py?rcl=bb9f32300c4ca57516ee1b7c35579fe75553b6c6&l=153
I'd like to have it for all our Android tester bots. E.g.:
* Nexus5X bots in: https://build.chromium.org/p/client.webrtc/waterfall
* Android testers in https://build.chromium.org/p/client.webrtc.perf/waterfall
* android_rel, android_dbg, android_arm64_rel in https://build.chromium.org/p/tryserver.webrtc/waterfall
I spent a little time trying to pass result_details=True and store_tombstones=True to our calls to runtest in scripts/slave/recipe_modules/chromium/api.py, but it didn't have any effect. I guess we're using different code paths. We're also planning to cleanup our own scripts/slave/recipe_modules/webrtc/steps.py so please keep ehmaldonado@ and myself in the loop if you end up making changes there.
I realized that the test results presentation generates a file like [1], which might be useful, but is not what we're looking for with this bug (i.e. a link in the result presentation to the logcat results).
I'll start looking into how to get them and display them.
Comment 1 by kjellander@chromium.org
, May 2 2017