1 # provision_CheetsUpdate 2 3 ## Running the autotest locally 4 5 In order to test your changes, run the autotest locally with: 6 7 ```shell 8 (chroot) $ test_that IP provision_CheetsUpdate --args='value=git_nyc-mr1-arc/cheets_arm-user/4885137' -b kevin 9 ``` 10 11 ## Running push\_to\_device manually 12 13 Go to [Android Build Status Dashboard](http://go/ab), select the target build, 14 download push\_to\_device.zip and the prebuilt image (e.g. cheets_arm-img-4885137.zip) 15 from the Artifacts tab. 16 17  18 19 ```shell 20 $ unzip push_to_device.zip -d ./ptd 21 $ python3 ./ptd/push_to_device.py --use-prebuilt-file ./cheets_arm-img-4885137.zip \ 22 --simg2img /usr/bin/simg2img --mksquashfs-path ./ptd/bin/mksquashfs \ 23 --unsquashfs-path ./ptd/bin/unsquashfs --shift-uid-py-path ./ptd/shift_uid.py IP --loglevel DEBUG 24 ``` 25 26 Warning: If the command fails, check run\_push\_to\_device method in 27 [provision_CheetsUpdate.py](https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/server/site_tests/provision_CheetsUpdate/provision_CheetsUpdate.py) for required params. 28 29 ## Updating the autotest 30 31 After you submit your changes, [Chrome OS lab deputy will push it to 32 prod](https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/chromeos-admin/push-to-prod). 33 Send a heads up to [Chrome OS lab 34 deputy](https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/chrome-os-infrastructure-deputy) 35 that this change is there. 36 37 Make sure that it is possible to pass 38 [presubmit](https://atp.googleplex.com/tests/arc++/presubmit?state=COMPLETED&testLabelName=PRESUBMIT&tabId=test_run) 39 after the change is pushed to prod. 40