Corrections when releasing usage information
[ Merge of http://go/wvgerrit/32940 ] Releasing usage entries may cause other entries to be moved or information updated. Instead of retrieving all entries once and trying to release them, refetch them after each release. Test: WV Unit/Integration tests Test: GTS tests (failures seen, but no additional failures due to this CL) Test: Playback testing using play movies and netflix. Bug: 65372189 Change-Id: I700e60834c7f711c9146dfd720f9cac014981311
This commit is contained in:
@@ -274,10 +274,11 @@ enum {
|
||||
kParseResponseError2 = ERROR_DRM_VENDOR_MIN + 261,
|
||||
kParseResponseError3 = ERROR_DRM_VENDOR_MIN + 262,
|
||||
kParseResponseError4 = ERROR_DRM_VENDOR_MIN + 263,
|
||||
kReleaseAllUsageInfoError6 = ERROR_DRM_VENDOR_MIN + 264,
|
||||
|
||||
// This should always follow the last error code.
|
||||
// The offset value should be updated each time a new error code is added.
|
||||
kErrorWVDrmMaxErrorUsed = ERROR_DRM_VENDOR_MIN + 263,
|
||||
kErrorWVDrmMaxErrorUsed = ERROR_DRM_VENDOR_MIN + 264,
|
||||
|
||||
// Used by crypto test mode
|
||||
kErrorTestMode = ERROR_DRM_VENDOR_MAX,
|
||||
|
||||
Reference in New Issue
Block a user