GetTitleTest hang on Android Tests caused device failure |
|||||
Issue descriptionA recent Catapult roll turned Android Tests red. https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/25684 In the stdio https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/25684/steps/Instrumentation%20test%20android_webview_test_apk/logs/stdio you can ctrl+f for "CommandTimeoutError". It came from File "/b/build/slave/Android_Tests/build/src/third_party/catapult/devil/devil/utils/cmd_helper.py", line 274, in GetCmdStatusAndOutputWithTimeout raise TimeoutError(output.getvalue()) Before the roll, it passed the CQ tests: https://codereview.chromium.org/1865503003 So this may only be flaky. Was this flaky previously or is this new?
,
Apr 5 2016
the catapult roll in question was this: https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/6d71ed5563f3..fa739d89dd6f It contains one CL that doesn't affect devil. I suspect this was a flake. The cronet DiskStorageTest#testPurgeOldVersion crash is almost certainly not related.
,
Apr 5 2016
Sorry, misidentified what happened here. It looks like org.chromium.android_webview.test.GetTitleTest#testGetTitleOnDataContainingNoTitle hung on 0cbc66fb032fdb7f. The next command run on that device, in tear down, hung as well. The resulting exception wasn't caught, and the step failed. I'm not sure why the test hung, that may well be flaky. The test runner should handle exceptions thrown by an individual device during tear down, though. -agrieve: this isn't actually related to the temporary file deletion
,
Apr 5 2016
,
Apr 7 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/58f87d1e9e2f2a8a24e047bafda9ce0abd7098a1 commit 58f87d1e9e2f2a8a24e047bafda9ce0abd7098a1 Author: jbudorick <jbudorick@chromium.org> Date: Thu Apr 07 16:56:13 2016 [Android] Handle exceptions thrown during instrumentation test teardown. BUG= 600855 Review URL: https://codereview.chromium.org/1860323002 Cr-Commit-Position: refs/heads/master@{#385788} [modify] https://crrev.com/58f87d1e9e2f2a8a24e047bafda9ce0abd7098a1/build/android/pylib/local/device/local_device_instrumentation_test_run.py
,
Apr 7 2016
the test runner should now gracefully handle this scenario. (GetTilteTest may still hang flakily, though) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cblume@chromium.org
, Apr 5 2016