New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 905365 link

Starred by 2 users
Status: WontFix
Owner:
█ linben@chromium.org
Last visit > 30 days ago
Closed: Nov 15
Cc:
█ victorhsieh@chromium.org
zwisler@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

login_VMSanity fails with "adbd is not running" error

Project Member Reported by benchan@chromium.org, Nov 14 
https://stainless.corp.google.com/browse/chromeos-autotest-results/257178658-chromeos-test/

11/14 09:39:33.133 DEBUG|          parallel:0030|   File "/usr/local/autotest/bin/parallel.py", line 18, in fork_start
11/14 09:39:33.133 DEBUG|          parallel:0030|     l()
11/14 09:39:33.133 DEBUG|          parallel:0030|   File "/usr/local/autotest/bin/job.py", line 488, in <lambda>
11/14 09:39:33.134 DEBUG|          parallel:0030|     l = lambda : test.runtest(self, url, tag, args, dargs)
11/14 09:39:33.134 DEBUG|          parallel:0030|   File "/usr/local/autotest/bin/test.py", line 117, in runtest
11/14 09:39:33.134 DEBUG|          parallel:0030|     job.sysinfo.log_after_each_iteration)
11/14 09:39:33.134 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/test.py", line 888, in runtest
11/14 09:39:33.135 DEBUG|          parallel:0030|     mytest._exec(args, dargs)
11/14 09:39:33.135 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
11/14 09:39:33.135 DEBUG|          parallel:0030|     _call_test_function(self.execute, *p_args, **p_dargs)
11/14 09:39:33.135 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function
11/14 09:39:33.135 DEBUG|          parallel:0030|     return func(*args, **dargs)
11/14 09:39:33.136 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/test.py", line 464, in execute
11/14 09:39:33.136 DEBUG|          parallel:0030|     postprocess_profiled_run, args, dargs)
11/14 09:39:33.136 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once
11/14 09:39:33.136 DEBUG|          parallel:0030|     self.run_once(*args, **dargs)
11/14 09:39:33.136 DEBUG|          parallel:0030|   File "/usr/local/autotest/tests/login_VMSanity/login_VMSanity.py", line 13, in run_once
11/14 09:39:33.137 DEBUG|          parallel:0030|     vm_sanity.VMSanity().Run()
11/14 09:39:33.137 DEBUG|          parallel:0030|   File "/usr/local/autotest/bin/vm_sanity.py", line 48, in Run
11/14 09:39:33.137 DEBUG|          parallel:0030|     self.RunCryptohomeTest()
11/14 09:39:33.137 DEBUG|          parallel:0030|   File "/usr/local/autotest/bin/vm_sanity.py", line 79, in RunCryptohomeTest
11/14 09:39:33.137 DEBUG|          parallel:0030|     arc.wait_for_android_process('org.chromium.arc.intent_helper')
11/14 09:39:33.138 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 489, in wait_for_android_process
11/14 09:39:33.138 DEBUG|          parallel:0030|     sleep_interval=_PROCESS_CHECK_INTERVAL_SECONDS)
11/14 09:39:33.138 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/utils.py", line 2756, in poll_for_condition
11/14 09:39:33.138 DEBUG|          parallel:0030|     value = condition()
11/14 09:39:33.138 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 485, in <lambda>
11/14 09:39:33.139 DEBUG|          parallel:0030|     condition = lambda: is_android_process_running(process_name)
11/14 09:39:33.139 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 386, in is_android_process_running
11/14 09:39:33.139 DEBUG|          parallel:0030|     output = adb_shell('pgrep -c -f %s' % pipes.quote(process_name))
11/14 09:39:33.139 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 222, in adb_shell
11/14 09:39:33.139 DEBUG|          parallel:0030|     output = adb_cmd('shell %s' % pipes.quote(cmd), **kwargs)
11/14 09:39:33.140 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 213, in adb_cmd
11/14 09:39:33.140 DEBUG|          parallel:0030|     wait_for_adb_ready()
11/14 09:39:33.140 DEBUG|          parallel:0030|   File "/usr/local/autotest/common_lib/cros/arc.py", line 184, in wait_for_adb_ready
11/14 09:39:33.140 DEBUG|          parallel:0030|     raise error.TestFail('adbd is not running.')
11/14 09:39:33.140 DEBUG|          parallel:0030| TestFail: adbd is not running.

Comment 2 by benchan@chromium.org, Nov 14

Owner: linben@chromium.org
linben: could you further triage as it seems related to arc.py

Comment 4 by linben@google.com, Nov 15

Cc: victorhsieh@chromium.org
Adding Victor who is swapping in for me for today

Comment 5 by victorhsieh@chromium.org, Nov 15 

Did this only happen on paladin?  It could be some problematic change in CQ. Also, the latest bob/scarlet-paladin are both green.

FWIW, I did see "adbd is not running" on canary days ago, but not any more.

Comment 6 by zwisler@google.com, Nov 15 

Yep, I think we've only seen this on paladin, not on release.

The latest reproduction was in a build at around midnight last night on both bob & scarlet, but yep, the last build for each was green.

Comment 7 by victorhsieh@chromium.org, Nov 15

Status: WontFix (was: Untriaged)
Cool.  Please re-open if you see this on release build.  I did see some camera crash on one of the crash but not the other, so this shouldn't be a persistent issue.  Thanks!
►

Sign in to add a comment