AFDO profile is too old on samus-pre-flight-R59 branch |
|||||
Issue descriptionThe samus-pre-flight-R59 builder will no longer allow the AFDO profile file to be updated, because it considers the current profile to be too old (see the failure in the AFDO stages of https://uberchromegw.corp.google.com/i/chromeos_release/builders/samus-pre-flight-branch%20release-R59-9460.B/builds/323) The timeout on this branch needs to be increased, until a new AFDO profile file gets generated.
,
Aug 1 2017
,
Aug 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/fdb8fae7e121c54a7c4e0dc2f2f72f0982c60c68 commit fdb8fae7e121c54a7c4e0dc2f2f72f0982c60c68 Author: Caroline Tice <cmtice@google.com> Date: Thu Aug 03 16:28:54 2017 Update AFDO time out on R59. Chrome has not updated for more than 14 days on R59, so now the AFDO mechanism will not allow AFDO profile files to update because it considers them too old. This issue is fixed in master/ToT, but not in R59, so we need to increase the timeout for AFDO on R59 for now. BUG= chromium:751209 TEST=None Change-Id: Ic1ad8f2fecc7e9c48178c8e6433eac0b45b1b505 Reviewed-on: https://chromium-review.googlesource.com/596512 Reviewed-by: Ting-Yuan Huang <laszio@chromium.org> Tested-by: Grace Kihumba <gkihumba@chromium.org> Commit-Queue: Caroline Tice <cmtice@chromium.org> Trybot-Ready: Caroline Tice <cmtice@chromium.org> [modify] https://crrev.com/fdb8fae7e121c54a7c4e0dc2f2f72f0982c60c68/cbuildbot/afdo.py
,
Aug 7 2017
,
Sep 25 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by laszio@chromium.org
, Aug 1 2017