summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
diff options
context:
space:
mode:
authorIgor Murashkin <iam@google.com>2019-01-22 14:31:38 -0800
committerIgor Murashkin <iam@google.com>2019-01-24 14:39:49 -0800
commit9d33ee90ce15c9cb296dc9b17da7e379ac81053b (patch)
tree41cf857ec26b595466fd0880c6c0b16a8d5e32bb /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp
parente9e439a47c10b5c3e8b8099ef16cf34c879c10ec (diff)
iorap: Handle binder failures by gracefully attempting to reconnect
Also hide down functionality behind setprops: * Debug logging (log.tag.ForwardingService VERBOSE) * Log.wtf instead of crashing (iorapd.forwarding_service.wtf_crash true) * Don't connect to binder if iorapd is disabled (iorapd.enable true) The primary benefit of this is that: a) If iorapd acts funny (or crashes) for any reason, it doesn't take down system server. b) If developer manually runs 'adb shell stop iorapd', it won't crash system server, and it doesn't need a restart ('adb shell stop/start') to re-establish the binder connection. Reconnections are done by sleeping forever in a 1-second loop. Bug: 72170747 Test: adb shell stop && adb shell start # and manually set adb shell props Test: atest system/iorap Change-Id: I789db8962dc8498b1028639274cd34a0310b84c1
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions