tree 1191a9e8e306287688fc50c8995bfced8c09798e
parent aba9a8cbce0b34455fd4b5a5e2a8d43ccebac417
author Yury Khmel <khmel@google.com> 1597891200 -0700
committer Commit Bot <commit-bot@chromium.org> 1597977690 +0000

arc: Add option to pin version for caches.

This is workaround for missing caches for release branches. I stil
have problems running PFQ with data collection on release branches. This
leads to some caches missing and noticable performance regression on
release branches.

The following scenarios are possible:
  * Generate caches using try_job and pin version manually for the
    release branch.
  * Run DataCollector on branch as ordinal TAST test. Once artifacts are
    ready, it automatically creates pin for the particular branch. So
    next builds will use last known good caches.

Using different versions are low risk on release branches.
  * GMS Core caches are GMS Core version dependent. We don't uprev GMS
  Core version in late stage of release branch.
  * ureadahead pack has risk to mismatch actual data however this should
  be minimal on release branches.

BUG=b:163823561
TEST=Locally, ./run_tests + monitor performance number from in-lab tests
on release branches.

Change-Id: I6cce5e4ed2271a0cab529d5326f3f3280148c20f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/2366100
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Yury Khmel <khmel@google.com>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Yury Khmel <khmel@google.com>
Auto-Submit: Yury Khmel <khmel@google.com>