diff options
author | Gilad Arnold <garnold@chromium.org> | 2013-04-17 10:00:55 -0700 |
---|---|---|
committer | ChromeBot <chrome-bot@google.com> | 2013-04-23 10:39:12 -0700 |
commit | 4fbe409cb84e9ae89f22c6f3e80580ee49dbc0a2 (patch) | |
tree | e2067593237107b4183be8ff823de7d3db743a88 /scripts/update_payload/checker_unittest.py | |
parent | 5502b56f34f9703cf053be46e4ea5685c0c9ac26 (diff) |
paycheck: perform payload integrity check by default
Currently, paycheck requires that --check, or one of its sub-options
(e.g. --type), is specified explicitly on the command-line in order to
trigger full payload checking. This means that invoking paycheck without
*any* optional arguments will amount to loading the payload manifest and
quitting. This is not a useful behavior.
Instead, we want payload integrity check to be the default behavior when
nothing else is requested. This also edits the help text to clarify the
distinction between verifying/applying a payload, and what guarantees
are provided wrt the actual CrOS update engine.
BUG=None
TEST=Payload checking triggered when no other argument is given; passes
unit/integrity testing.
Change-Id: I8199813d4654f5598fcf152a3cdc62efbfc533da
Reviewed-on: https://gerrit.chromium.org/gerrit/48373
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Darin Petkov <petkov@chromium.org>
Commit-Queue: Gilad Arnold <garnold@chromium.org>
Diffstat (limited to 'scripts/update_payload/checker_unittest.py')
0 files changed, 0 insertions, 0 deletions