Manually uprev Chrome to 58.0.2993.0 for Chrome OS |
|||||||
Issue descriptionChrome has not uprev'd for 3 days. Currently the chrome ToT informational builders are all green. The only chrome PFQ failure from last night was a flaky infra issue (a DUT became unpingable). I'm going to try to roll chrome forward. +cc all the sheriffs in case I mess it up.
,
Jan 26 2017
I found docs for rolling forward: https://yaqs.googleplex.com/eng/q/5592011371970560 - changing this bug to use the template. Due to a series of infrastructure issues (unpingable DUTs on falco-chrome-pfq), we have not had a Chrome uprev since Monday Jan 23. This PFQ run: https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/3890 only had one failing slave: https://uberchromegw.corp.google.com/i/chromeos/builders/falco-chrome-pfq/builds/5250 and the failure was due to a transient issue
,
Jan 26 2017
https://chrome-internal-review.googlesource.com/#/c/321165/ https://chromium-review.googlesource.com/#/c/433362/ Generated with: cros uprevchrome --debug --pfq-build 1285523 --cred-dir=/home/jamescook/trunk/prod_cidb_readonly/ --bug='chromium:685675' --draft
,
Jan 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/a3db52fae0238ce9381d8355483acaeaa257ebf9 commit a3db52fae0238ce9381d8355483acaeaa257ebf9 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Thu Jan 26 18:44:45 2017 Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1285523, build_number 3890 Marking set of ebuilds as stable amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST daisy-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST amd64-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo'} and updated Manifest" "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo'} and updated Manifest" Marking latest_release for chromium-source ebuild with version 58.0.2993.0 as stable. Marking latest_release for chromeos-chrome ebuild with version 58.0.2993.0 as stable. BUG= chromium:685675 TEST=None CQ-DEPEND=*I718bf2238197753d8557f17301c85f5df9725c16 Change-Id: I1e3131989c07f26ab316203ebd875b5a5e0df96b Reviewed-on: https://chromium-review.googlesource.com/433362 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: James Cook <jamescook@chromium.org> Reviewed-by: James Cook <jamescook@chromium.org> [rename] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/chromeos-chrome-58.0.2993.0_rc-r1.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf [rename] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromium-source/chromium-source-58.0.2993.0_rc-r1.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/Manifest [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf
,
Jan 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/a3db52fae0238ce9381d8355483acaeaa257ebf9 commit a3db52fae0238ce9381d8355483acaeaa257ebf9 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Thu Jan 26 18:44:45 2017 Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1285523, build_number 3890 Marking set of ebuilds as stable amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST daisy-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST amd64-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo'} and updated Manifest" "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2993.0_rc-r1.afdo'} and updated Manifest" Marking latest_release for chromium-source ebuild with version 58.0.2993.0 as stable. Marking latest_release for chromeos-chrome ebuild with version 58.0.2993.0 as stable. BUG= chromium:685675 TEST=None CQ-DEPEND=*I718bf2238197753d8557f17301c85f5df9725c16 Change-Id: I1e3131989c07f26ab316203ebd875b5a5e0df96b Reviewed-on: https://chromium-review.googlesource.com/433362 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: James Cook <jamescook@chromium.org> Reviewed-by: James Cook <jamescook@chromium.org> [rename] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/chromeos-chrome-58.0.2993.0_rc-r1.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf [rename] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromium-source/chromium-source-58.0.2993.0_rc-r1.ebuild [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos-base/chromeos-chrome/Manifest [modify] https://crrev.com/a3db52fae0238ce9381d8355483acaeaa257ebf9/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf
,
Jan 26 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-partner-overlay/+/0a5c0d642cd8be556210a5232df3f345408017d4 commit 0a5c0d642cd8be556210a5232df3f345408017d4 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Thu Jan 26 18:44:46 2017
,
Jan 27 2017
Manual uprev worked. There has also been a successful PFQ run, so we're on 58.0.2994.0 now. Woo hoo!
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jamescook@chromium.org
, Jan 26 2017