diff options
| author | Tom Cherry <tomcherry@google.com> | 2019-11-12 16:21:20 -0800 |
|---|---|---|
| committer | Tom Cherry <tomcherry@google.com> | 2019-11-13 12:41:34 -0800 |
| commit | 18278d2e9ccb9e7fdb8391055c56d1b35b3e39a6 (patch) | |
| tree | cc46ed78a58235f4a011f535f8f4eaa53f8a3ee2 /trusty/coverage/coverage_test.cpp | |
| parent | e91c76b2104792d839b2bd3036e7e265427dcdc1 (diff) | |
init: make triggering shutdown from vendor_init better
Previously, we assumed that TriggerShutdown() should never be called
from vendor_init and used property service as a back up in case it
ever did. We have since then found out that vendor_init may indeed
call TriggerShutdown() and we want to make it just as strict as it is
in init, wherein it will immediately start the shutdown sequence
without executing any further commands.
Test: init unit tests, trigger shuttdown from init and vendor_init
Change-Id: I1f44dae801a28269eb8127879a8b7d6adff6f353
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions