summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorSuprabh Shukla <suprabh@google.com>2018-06-20 17:28:26 -0700
committerSuprabh Shukla <suprabh@google.com>2018-06-20 17:28:28 -0700
commit0e4510df376eb15f1abcda78b9baf078f74f49b9 (patch)
treeea83043ba3935f5b46858f2d89b1e26af10adbd7 /tools/aapt2/java/JavaClassGenerator_test.cpp
parentc675f31fdcc519a5eab8df135c49a277e61ab48b (diff)
Logging a wtf if alarm delivery gets stuck
If alarm delivery is stuck, detect and log a wtf. This will help us catch relevant information sooner and also indicate how frequently this happens. Otherwise this is something that can easily go unnoticed and is usually hard to debug once the alarms are running as expected again. Test: Builds, boots, existing alarm tests pass. adb shell dumpsys alarm Bug: 78560047 Change-Id: Ife881f2c9649b8dfd87ba05a425483375361da64
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions