Interesting that the build has actual separate steps named android_webview_test_apk and android_webview_test_apk.android_webview_test_apk that are both failing.

However it looks like it's actually just one test run (both reported the same test failing, but android_webview_test_apk.android_webview_test_apk was the one with full logs) but logged as separate steps. 

I'm not sure yet how to proceed with this.  martiniss@ - do you know why an Android builder would record test steps this way?

That's how milo shows nested steps. The buildbot page (https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/7686) shows the step as nested.

I think the android test runner has a bit of special logic to mark the root step as failing. 

We can probably just merge these by prefix.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot