summaryrefslogtreecommitdiff
path: root/scripts/update_payload/test_utils.py
diff options
context:
space:
mode:
authorJae Hoon Kim <kimjae@chromium.org>2020-05-11 20:18:49 -0700
committerCommit Bot <commit-bot@chromium.org>2020-05-21 01:54:11 +0000
commit29a80e0af8162fce0c79a0187adab2c9d3d9273a (patch)
tree8382cf6e43588caac4a1df7bc0b8858a40de49d6 /scripts/update_payload/test_utils.py
parentc1f3692605e422e17a8ef8f3d2148e8e6ef6316e (diff)
update_engine: Fix [Memory|File]Storage partial inconsistency
|Prefs::MemoryStorage| and |Prefs::FileStorage| had inconsistency when dealing with operations through |StorageInterface|, this change keeps the implementations more consistent. This keeps the underlying |StorageInterface| impementations behaving as similar as can be whether |[Memory|File]Storage| is used. Passing a namespace to |Prefs::FileStorage| backed |Pref| is no longer recursive in order to restrict to deleting keys. To delete all keys within a namespace, callers can use |Prefs::GetSubKeys(...)| and |Prefs::Delete(...)| accordingly. BUG=chromium:928805 TEST=FEATURES=test emerge-$B update_engine Change-Id: I3ea8b51e14b1405ca1cdef66f858a18d124ca0aa Reviewed-on: https://chromium-review.googlesource.com/c/aosp/platform/system/update_engine/+/2195624 Tested-by: Jae Hoon Kim <kimjae@chromium.org> Commit-Queue: Jae Hoon Kim <kimjae@chromium.org> Reviewed-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Andrew Lassalle <andrewlassalle@chromium.org>
Diffstat (limited to 'scripts/update_payload/test_utils.py')
0 files changed, 0 insertions, 0 deletions