It looks like Lollipop Phone Tester is not stable.

By checking flakiness dashboard for each individual failing tests in chrome_public_test_apk:

testExportMenuItemNoLock https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=chrome_public_test_apk&tests=testExportMenuItemNoLock
testCastTwoVideosSamePage https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=chrome_public_test_apk&tests=testCastTwoVideosSamePage
testPlayNewVideoNewPageSameTab https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=chrome_public_test_apk&tests=testPlayNewVideoNewPageSameTab
testFailCreateRoute https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=chrome_public_test_apk&tests=testFailCreateRoute

It looks like these tests are in good shape except on Lollipop Phone Tester, so I think there should be something wrong with this builder.

jbudorick@, could you please help to triage this issue?

Latest build has more failing tests https://uberchromegw.corp.google.com/i/chromium.android/builders/Lollipop%20Phone%20Tester/builds/17180

Latest build succeed, closing this issue.

Hmm, the latest build failed again..

We're still getting a few failures, eg:

Build 17227 failed on SavePasswordsPreferencesTest#testExportMenuItemNoLock
Build 17230 failed on SavePasswordsPreferencesTest#testExportMenuEnabled
Build 17231 failed on SavePasswordsPreferencesTest#testViewPasswordNoLock and SavePasswordsPreferencesTest#testExportMenuItemNoLock

Sometimes there are no logs since the failure was a TIMEOUT (eg in Build 17231), however when we do get logs, the failure is:

android.support.test.espresso.NoMatchingViewException: No views in hierarchy found matching: with string from resource id: <2131427596>[password_export_set_lock_screen] value: Turn on screen lock in Settings to export your passwords from this device

If this turns out to be a NoMatchingViewException-related failure,  bug 793437  needs reopening. However, it might still be that NoMatchingViewException is just highlighting the some issue of the device. If there is a way to see the device running the test, it would be great to know whether a toast is displayed at the end of the test.

This is most likely  bug 787056  (general infra flakiness), but I'll take a look when I get a chance.