init_kill_services_test: wait 120s for apexd
This is likely waiting for the Java garbage collector to run, and due to the lockless implementation of BinderProxyNativeData and BpBinder, it's very difficult to efficiently force this object to be deleted. Change-Id: I4df667b9b47327967a43d75664fb506b8704f905 Fixes: 285458033 Test: N/A
This commit is contained in:
parent
90fc835d48
commit
14e7b76dcf
1 changed files with 1 additions and 1 deletions
|
@ -32,7 +32,7 @@ void ExpectKillingServiceRecovers(const std::string& service_name) {
|
|||
// b/280514080 - servicemanager will restart apexd, and apexd will restart the
|
||||
// system when crashed. This is fine as the device recovers, but it causes
|
||||
// flakes in this test.
|
||||
ASSERT_TRUE(WaitForProperty("init.svc.apexd", "stopped", 60s))
|
||||
ASSERT_TRUE(WaitForProperty("init.svc.apexd", "stopped", 120s))
|
||||
<< (system("cat /dev/binderfs/binder_logs/state"), "apexd won't stop");
|
||||
|
||||
LOG(INFO) << "hello " << service_name << "!";
|
||||
|
|
Loading…
Reference in a new issue