summaryrefslogtreecommitdiff
path: root/scripts/update_payload/test_utils.py
diff options
context:
space:
mode:
authorToni Barzic <tbarzic@google.com>2018-10-11 14:37:30 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-10-16 02:57:34 -0700
commit61544e6b7705b6252efa8eaabc7ed2b3a1169b9a (patch)
treeb2b3e48a254cdc3d06e0b2fe580cd1d55aa853be /scripts/update_payload/test_utils.py
parent26bb865b2743a9767b42840278ac032db274d5f3 (diff)
Do not report NEED_PERMISSION_TO_UPDATE for non-critical OOBE updates
As part of https://crbug.com/889948, Chrome OS OOBE will start properly handling NEED_PERMISSION_TO_UPDATE update status (instead of treating it as any other error) - it will display a message to the user informing them that the update can cause overage changes on mobile network, and ask their permission to proceed. Currently, NEED_PERMISSION_TO_UPDATE status is reported over cellular for non-critical updates during OOBE, even though these are later ignored by the update engine. This can produce sub-optimal UX where the user is prompted to proceed with update, even though the update gets skipped when attempted. This CL makes sure that kNonCriticalUpdateInOOBE error status has precedence over kOmahaUpdateIgnoredOverCellular in omaha_request_action (the latter one causes NEED_PERMISSION_TO_UPDATE status) BUG=chromium:889948 TEST=run OOBE with update engine thinking it's on cellular network, verify that the user sees prompt about possible overage charges for critical updates only (dut setup included patching update engine to treat ethernet connection as cellular, and running devserver locally with and without --critical_update flag) Change-Id: If87b9477fd7f826892b1aeedc1017d11b1a0af32 Reviewed-on: https://chromium-review.googlesource.com/1277708 Commit-Ready: Toni Baržić <tbarzic@chromium.org> Tested-by: Toni Baržić <tbarzic@chromium.org> Reviewed-by: Amin Hassani <ahassani@chromium.org>
Diffstat (limited to 'scripts/update_payload/test_utils.py')
0 files changed, 0 insertions, 0 deletions