Allow brillo_update_payload --verify to run update_payload paycheck tests |
|
Issue descriptionCurrently, "brillo_update_payload verify" only applies the given payload to a source image (or no source image if full payload) and verifies that the update went well. A better solution is to allow brillo_update_payload to run the checks in the update_engine/scripts. This can be done by at least passing the path to update_endine/scripts location. With this change, in addition to covering more tests, the possibility of mistakenly breaking canaries is reduced because canary releases run paygenbuild and paygentest autotests which uses the same libraries (update_engine/scripts) to perform some parts of the tests.
,
Dec 7 2017
I see. It is a good command to have though. Sometimes I run "brillo_update_payload verify" but I forget to run paycheck scripts and later it bites me. The problem is all the paycheck tests are based on kernel and rootfs partitions and won't be easily aligned to variable number of partitions in AOSP. So we have to somehow upgrade those behaviors. |
|
►
Sign in to add a comment |
|
Comment 1 by senj@chromium.org
, Dec 7 2017