summaryrefslogtreecommitdiff
path: root/common/error_code.h
diff options
context:
space:
mode:
authorAmin Hassani <ahassani@chromium.org>2018-05-16 13:34:00 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-05-23 12:50:53 -0700
commit80f4d4cefb5270960d17cd347d71594e97c7a954 (patch)
tree115e34a098a80a083e975b0854e6e7615653879d /common/error_code.h
parent761be2cfd245cd8378bf8efc65b39a31cc065809 (diff)
update_engine: Report VPD write failure to UMA
Currently we see many first actives to come from non-FSI images. But we have not been able to figure out why. This CL, reports a new error kFirstActiveOmahaPingSentPersistenceError when writing the first active omaha flag into VPD fails. This allows us to see if that is the actual cause of the problem. CL:1062659 adds the enum value on the Chrome side. BUG=chromium:833980 TEST=unittests TEST=precq Change-Id: I65e233c5f895489ba905494fb20d7b00d0c4af10 Reviewed-on: https://chromium-review.googlesource.com/1062662 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Ben Chan <benchan@chromium.org>
Diffstat (limited to 'common/error_code.h')
-rw-r--r--common/error_code.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/common/error_code.h b/common/error_code.h
index c301155d..a7fee2a2 100644
--- a/common/error_code.h
+++ b/common/error_code.h
@@ -78,6 +78,7 @@ enum class ErrorCode : int {
kUpdatedButNotActive = 52,
kNoUpdate = 53,
kRollbackNotPossible = 54,
+ kFirstActiveOmahaPingSentPersistenceError = 55,
// VERY IMPORTANT! When adding new error codes:
//