diff options
| author | Mohammad Samiul Islam <samiul@google.com> | 2020-08-12 15:15:48 +0100 |
|---|---|---|
| committer | Mohammad Samiul Islam <samiul@google.com> | 2020-11-04 19:15:42 +0000 |
| commit | 558f0c88428face4371a9a24a7e620eaf33c2e6a (patch) | |
| tree | 283673c633fd43b695da04ad168e88f1fa2f7645 /rs/java/android/renderscript/ProgramStore.java | |
| parent | e5e23888448c04f1abfcaa65de12f913b5b4cbc6 (diff) | |
Improve logging for why a staged session was reverted
mFailureReason gets populated with actual reason when we try to resume
the staged session in checkpointing mode. But, if the device has a
native crash due to which the device reboots even before we attempt to
"resume" staged session, then it will never get populated.
As such, during boot loops that occur earlier than "resume" of staged
session, we end up logging nothing.
In this CL, we improve on the scenario by falling back to using
mNativeFailureReason if mFailureReason is empty. But this only works if
our staged session contains APEX package in it. For apk-only staged
sessions, we will still be logging blanks.
Bug: 163787002
Test: atest ApexRollbackTests#testReasonForRevertIsLoggedDuringBootloop
Change-Id: I5cd1733d66aa0b30855803b95eb9818dc81aa0d7
Merged-In: I5cd1733d66aa0b30855803b95eb9818dc81aa0d7
(cherry picked from commit a4cb493bdb69488a9b94aae627545aa91db55083)
Diffstat (limited to 'rs/java/android/renderscript/ProgramStore.java')
0 files changed, 0 insertions, 0 deletions