summaryrefslogtreecommitdiff
path: root/framework/java/android/bluetooth/BluetoothDevice.java
diff options
context:
space:
mode:
authorWilliam Escande <wescande@google.com>2022-04-18 23:35:36 -0700
committerWilliam Escande <wescande@google.com>2022-04-19 17:11:58 -0700
commit926d29cae688087d56a8570d824c4375e089d63d (patch)
tree3f901e2c8290d7ea09f241358836920e883a1e1d /framework/java/android/bluetooth/BluetoothDevice.java
parent99dc2fa04da6254cd9dc8d948e8bf0023622d451 (diff)
Silent death test to no longer have a stack crash
Stack crash in log are raising warning for Realtime Stability insight By using the ScopedSilentDeath, we mute the SIGABRT signal (and other but theses are not important here). I tried to minimized the scope where signal where silent in order to not miss a crash in a part of the test that is not supposed to fail I also verified that a non death in a death test was still reported as a test failure (the ScopedSilentDeath does not prevent the ASSERT !) This add a dependency to libbase, but because it's for the test I don't think this is an issue Test: atest net_test_osi Test: atest net_test_btpackets Then on both test, looks at the log and notice the death test did not write the stack in the log Fix: 223765254 Ignore-AOSP-First: This crash is only due to apex static linking and this is not on AOSP Change-Id: Ib6241b5682b5446c7fedd6ef590569f690cc826a
Diffstat (limited to 'framework/java/android/bluetooth/BluetoothDevice.java')
0 files changed, 0 insertions, 0 deletions