Pretty much all of the failures on this bot in the past few days can be attributed to these two tests: PaymentRequestNoShippingTest#testAddEmptyNameOnCardAndCancel https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5295 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5294 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5291 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5288 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5286 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5285 PaymentRequestNoShippingTest#testAddInvalidCardNumberAndCancel https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5293 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5292 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5291 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5289 https://build.chromium.org/p/chromium.android/builders/Jelly%20Bean%20Tester/builds/5287 These too (like Issue 631989 ) are TimeoutExceptions ("waitForCallback timed out!") after a ten second timeout. Consider marking as @LargeTest to increase the timeout?
peter@, this is more likely due to waiting for incorrect callbacks. I'll fix it without using @LargeTest.
Comment 1 by rouslan@chromium.org
, Jul 27 2016