testExportMenuItemNoLock flakes on chromium.android/Lollipop Phone Tester |
|||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ctzsm@google.com chrome_public_test_apk failing on chromium.android/Lollipop Phone Tester Builders failed on: - Lollipop Phone Tester: https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester testExportMenuItemNoLock flakes on chromium.android/Lollipop Phone Tester Flakiness dashboard https://test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&testType=chrome_public_test_apk&tests=testExportMenuItemNoLock
,
Dec 8 2017
,
Dec 8 2017
Wait, the test passed on Lollipop Tablet Tester with only one failure, it seems that this is not Android version related, but something wrong with Lollipop Phone Tester?
,
Dec 8 2017
Actually no failure on Lollipop Tablet Tester.
,
Dec 8 2017
,
Dec 12 2017
Thanks for reporting this and the related bug. The failing test (and also the related testViewPasswordNoLock) fail to "see" a toast. While the Espresso framework suggests to use onData instead of onView, that's likely a red herring, because the toast is not part of an AdapterView, IIUC. One explanation would be that perhaps the toast is shown too late for the test to notice. I'm not sure if there is a event the test should wait for before checking for the existence of the toast -- advice welcome! (Normally, Espresso should ensure that pending UI tasks are finished, but there may be exceptions.) I'm OOO until the second third of January, so will not be able to help until then. If the tests specifically (as opposed to the whole builder) turns out to be problematic, please disable it and assign this to me. I can try if I can reproduce on a phone with a Lollipop build.
,
Dec 12 2017
Attaching the error log from a sample trybot run.
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ctzsm@chromium.org
, Dec 8 2017Owner: vabr@chromium.org
Status: Assigned (was: Available)