Issue metadata
Sign in to add a comment
|
cheets_PlayStoreTest Test failing on Sand device with "adb is not ready in 60 seconds." error. |
||||||||||||||||||||
Issue description
Sample failure,
05/31 15:47:55.339 DEBUG| autotest:1281| AUTOTEST_STATUS::START ---- ---- timestamp=1527806874 localtime=May 31 15:47:54
05/31 15:47:55.340 INFO | server_job:0218| START ---- ---- timestamp=1527806874 localtime=May 31 15:47:54
05/31 15:47:55.440 DEBUG| autotest:1281| AUTOTEST_STATUS:: START cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527806874 localtime=May 31 15:47:54
05/31 15:47:55.441 INFO | server_job:0218| START cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527806874 localtime=May 31 15:47:54
05/31 15:52:53.630 DEBUG| autotest:1281| AUTOTEST_STATUS:: FAIL cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527807172 localtime=May 31 15:52:52 Unhandled Exception: Could not find app in results
05/31 15:52:53.631 INFO | server_job:0218| FAIL cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527807172 localtime=May 31 15:52:52 Unhandled Exception: Could not find app in results
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: Traceback (most recent call last):
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: return func(*args, **dargs)
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/common_lib/test.py", line 495, in execute
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: dargs)
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: postprocess_profiled_run, args, dargs)
05/31 15:52:53.631 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: self.run_once(*args, **dargs)
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/tests/cheets_PlayStoreTest/cheets_PlayStoreTest.py", line 183, in run_once
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: self.install_app_from_play_store()
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/tests/cheets_PlayStoreTest/cheets_PlayStoreTest.py", line 113, in install_app_from_play_store
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: search_app()
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: File "/usr/local/autotest/tests/cheets_PlayStoreTest/cheets_PlayStoreTest.py", line 103, in search_app
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: raise Exception('Could not find app in results')
05/31 15:52:53.632 DEBUG| autotest:1281| AUTOTEST_STATUS:: Exception: Could not find app in results
05/31 15:52:53.646 DEBUG| autotest:1281| AUTOTEST_STATUS:: END FAIL cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527807172 localtime=May 31 15:52:52
05/31 15:52:53.646 INFO | server_job:0218| END FAIL cheets_PlayStoreTest cheets_PlayStoreTest timestamp=1527807172
https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-05-30&last_date=2018-06-01&test=cheets_PlayStoreTest&model=sand&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&status=ALERT&status=RUNNING&status=TEST_NA&status=NOSTATUS&status=NOT_RUN&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=false&exclude_acts=false&exclude_retried=false&exclude_non_production=false
,
Jun 1 2018
This blocked the boards from the latest push. Hoping to get the right eyes on this for triage. This blocked banon as well as sand. Who's the best group for CTS Autotest failures?
,
Jun 1 2018
,
Jun 1 2018
This seems like a flaky test, it passed most of the time. https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-05-05&last_date=2018-06-01&test=cheets_PlayStoreTest&build=R67.*&model=sand&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&status=ALERT&status=RUNNING&status=TEST_NA&status=NOSTATUS&status=NOT_RUN&exclude_cts=false&exclude_not_run=false&exclude_non_release=false&exclude_au=false&exclude_acts=false&exclude_retried=false&exclude_non_production=false It looks like dhaddock@ has had the most recent CLs on this test to try to make it more robust... any ideas on if this is actionable?
,
Jun 1 2018
,
Jun 1 2018
,
Jun 1 2018
"adb is not ready in 60 seconds" is just a general failure from any test that inherits from ArcTest and fails to connect to adb at the start of the test during initialize(). The failures for the cant find SEARCH image include screenshots (attached). It looks like the Play Store did not get setup properly or something. The test tries 5 times so this seems like something other than flake
,
Jun 1 2018
,
Jun 1 2018
So if adb is failing to connect and the play store doesn't seem to be able to connect either, could it be a network issue?
,
Jun 1 2018
+dhaddock, should you be the owner on this ?
,
Jun 1 2018
No I don't think so. Somebody who understand what that error in the screenshot means should. +khmel is my guess
,
Jun 2 2018
,
Jun 2 2018
,
Jun 2 2018
,
Jun 2 2018
This seems like a serious issue if this can be reproduced manually too and not just a test issue. A few logs that stood out from logcat: 06-01 10:08:00.155 783 875 D Volley : [128] e.a: HTTP response for request=<[ ] https://android.clients.google.com/fdfe/userSettings 0xe8d195d1 NORMAL 8> [lifetime=5149], [size=7116], [rc=500], [retryCount=0] 06-01 10:08:00.155 783 875 E Volley : [128] e.a: Unexpected response code 500 for https://android.clients.google.com/fdfe/userSettings 06-01 10:08:00.411 783 876 I Finsky : [129] com.google.android.finsky.api.a.cp.a(459): com.google.wireless.android.finsky.devicefe.exception.FinskyDfeRpcException: com.google.net.rpc3.client.RpcClientException: <eye3 title='/UserDataService.ListPreferences, INTERNAL'/> APPLICATION_ERROR;finsky.userdata/UserDataService.ListPreferences;com.google.spanner.SpannerException: generic::DEADLINE_EXCEEDED: Deadline missed
,
Jun 4 2018
Is this issue limited to banon and sand? A bit time critical given the stable schedule. Would like to determine the scope and likelihood of resolution / RBS consideration. Thanks
,
Jun 4 2018
> This seems like a serious issue if this can be reproduced manually too and not just a test issue. Is this actually happening manually? I don't see anyone saying that comment#7: I think the adb connection failure is still flake, as if you go back in the results in comment#4 and other invocations, you see this occasional problem. The play store search / app not found failures seem like they could easily be Play Store issues, and each branch is newly failing, despite no seemingly relevant changes landing in any of the branches. IMO this is not a great test because it's not hermetic. Adding constables, this test should be more stable, but I don't think it's RBS. We should try to figure out why ADB can't connect in 5 retries sometimes, and we should think about ways to separate out ways to test install and use of the Play Store hermetically, and a non-hermetic test that could actually search for results.
,
Jun 26 2018
,
Jul 10
"adb is not ready in 60 seconds" failure is not seen anymore in the latest builds. "Can not find SEARCH image" failure is Bug 848824 . |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by aashuto...@chromium.org
, Jun 1 2018