commit 14e7b76dcf917041b2d2e6256c850fe9f987c35d
author Steven Moreland <smoreland@google.com> Thu Jun 22 18:56:07 2023 +0000
committer Steven Moreland <smoreland@google.com> Thu Jun 22 18:56:09 2023 +0000
tree 2dee6fb39712ab746df7ab45984c098daeff3876
parent 90fc835d48397ead61de54d4b0ddb99c656bf74d

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

init/test_kill_services/init_kill_services_test.cpp

diff --git a/init/test_kill_services/init_kill_services_test.cpp b/init/test_kill_services/init_kill_services_test.cpp
index dd46064..510ad8a 100644
--- a/init/test_kill_services/init_kill_services_test.cpp
+++ b/init/test_kill_services/init_kill_services_test.cpp
@@ -32,7 +32,7 @@
     // 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 << "!";