summaryrefslogtreecommitdiff
path: root/scripts/update_payload/checker_unittest.py
diff options
context:
space:
mode:
authorAmin Hassani <ahassani@google.com>2017-07-11 17:10:50 -0700
committerchrome-bot <chrome-bot@chromium.org>2017-07-18 00:32:49 -0700
commit7ecda265a87236e83cf820364947a1618872b6be (patch)
tree39a5e3c3b8166289074bfb814f9cad8c8f186371 /scripts/update_payload/checker_unittest.py
parent39f571439821118c9ee5b36131e851206b819074 (diff)
Open partitions with O_DSYNC flag only if the update is periodic.
Currently when updating we always open the target partition with flag O_DSYNC (CL:562552), but this makes all infrastructure operations like 'cros flash', provisioning, force update, paygen, etc much slower. This changes the update engine to only add O_DSYNC flag if an update is triggered by periodic checks (not interactively forced). This means if the user clicks on 'check for update' it will be an interactive update and O_DSYNC will not be used. This change keeps the AOSP partitions open without O_DSYNC flag. This CL uses non-interactive mode for all unit tests but currently there are no integration test like provisioning for triggering periodic updates. Currently 'parrot' board canaries (only board with rotating HDD) is failing due to timeouts related to slow updates. This CL potentially will clear that problem. TEST=cros_workon_make --test, installed an image with/out the O_DSYCN flag and measured the 'cros flash' time. BUG=chromium:738027 Change-Id: If45fcf5e798b9c9353e09021ad812c859d983a65 Reviewed-on: https://chromium-review.googlesource.com/567360 Commit-Ready: Amin Hassani <ahassani@chromium.org> Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org>
Diffstat (limited to 'scripts/update_payload/checker_unittest.py')
0 files changed, 0 insertions, 0 deletions