diff options
| author | Tej Singh <singhtejinder@google.com> | 2019-06-07 17:23:30 -0700 |
|---|---|---|
| committer | Tej Singh <singhtejinder@google.com> | 2019-06-07 17:56:24 -0700 |
| commit | cbf2c6402411d1fac7dd04c728d7bcc6b6a986d3 (patch) | |
| tree | afa77f876a1189d61641b7e9ccdbbf5ac7f82923 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 2aa255a74656e448b28b1f258d25bed18f2d6396 (diff) | |
Persist metric activation across beta4/5 ota
In beta 4, activeEventActivation proto object does not have a state
field and assumed to be active if it is written to disk. In beta 5, we
add a state field to support persisting metric activation status across
a system server crash. However, if a device updated from beta 4 to 5, we
don't have any knowledge of the state when we read. Therefore, assume
the lack of the state field as the event activation should be active for
the provided ttl.
Bug: 134795027
Test: used flashstation to flash a device to beta 4. Then manually push
and activate a simple config. Then use vendor/google/tools/flashall to
update to qt-dev + this change. Manually ensure metric/config are still
active.
Test: gts-tradefed run gts-dev --module GtsStatsdHostTestCases
Test: bit statsd_test:*
Change-Id: I8594d04efaa2ae1f669113aaffd33e5fa5851e73
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions