Searched refs:completed (Results 1 – 17 of 17) sorted by relevance
| /system/unwinding/libunwindstack/tests/ |
| D | UnwindTest.cpp | 229 void WaitForRemote(pid_t pid, uint64_t addr, bool leave_attached, bool* completed) { in WaitForRemote() argument
230 *completed = false; in WaitForRemote()
243 *completed = true; in WaitForRemote()
245 if (!*completed || !leave_attached) { in WaitForRemote()
248 if (*completed) { in WaitForRemote()
267 bool completed; in TEST_F() local
268 WaitForRemote(pid, reinterpret_cast<uint64_t>(&g_ready_for_remote), true, &completed); in TEST_F()
269 ASSERT_TRUE(completed) << "Timed out waiting for remote process to be ready."; in TEST_F()
291 bool completed; in TEST_F() local
292 WaitForRemote(pid, reinterpret_cast<uint64_t>(&g_ready_for_remote), true, &completed); in TEST_F()
[all …]
|
| /system/sepolicy/prebuilts/api/31.0/private/ |
| D | ueventd.te | 6 # to init that cold boot has completed.
|
| /system/sepolicy/private/ |
| D | ueventd.te | 6 # to init that cold boot has completed.
|
| /system/core/bootstat/ |
| D | bootstat.rc | 58 # sys.bootstat.first_boot_completed=0 - first boot completed trigger wasn't processed yet.
59 # sys.bootstat.first_boot_completed=1 - first boot completed trigger was processed and
60 # record_boot_complete was called. Subsequent boot completed
|
| /system/chre/apps/test/common/proto/ |
| D | chre_settings_test.proto | 21 // TEST_COMMAND message has completed. No payload.
|
| /system/extras/memory_replay/traces/ |
| D | README | 67 Indicates that the thread <tid> has completed.
|
| /system/core/fs_mgr/libsnapshot/ |
| D | PowerTest.md | 36 …ble of rebooting normally without user intervention. Once the merge has completed, the test will r…
|
| /system/iorap/src/binder/ |
| D | iiorap_impl.cc | 151 void ReplyWithResult(const RequestId& request_id, bool completed, TaskResult result) { in ReplyWithResult() argument
162 if (completed) { in ReplyWithResult()
|
| /system/sepolicy/prebuilts/api/30.0/public/ |
| D | ueventd.te | 63 # to init that cold boot has completed.
|
| /system/bt/gd/cert/ |
| D | gd_device.py | 672 completed = self.adb.getprop("sys.boot_completed")
673 if completed == '1':
|
| /system/core/fs_mgr/libsnapshot/android/snapshot/ |
| D | snapshot.proto | 127 // Post-merge cleanup steps could not be completed due to a transient
|
| /system/chre/chpp/ |
| D | README.md | 149 …end() returns before completely consuming buf and len (e.g. the send is completed at a later time)…
|
| /system/core/fastboot/ |
| D | README.md | 43 c. OKAY -> the requested command completed successfully. Go to #5
|
| /system/apex/docs/ |
| D | howto.md | 332 verification is completed before returning. On S devices the `--wait` option is
|
| /system/update_engine/ |
| D | README.md | 100 completed and the user needs to reboot the system. At this point, until the user
|
| /system/core/init/ |
| D | README.md | 971 /system to /. The contents of the ramdisk are freed after mounting has completed.
|
| /system/core/rootdir/ |
| D | init.rc | 935 # completed and apexd.status becomes "ready".
|