New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 686840 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Manually uprev Chrome 58.0.2997.0 for Chrome OS

Project Member Reported by x...@chromium.org, Jan 30 2017

Issue description

Due to provisions DeviceNotPingable failure (Issue 683304), we have not had a Chrome uprev since Jan/27. 

This PFQ run https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/3906 
only had one failing salve 
https://uberchromegw.corp.google.com/i/chromeos/builders/falco-chrome-pfq/builds/5266 (DeviceNotPingable failure as seen in Issue 683304) and meets all the criteria to be manually upreved.

Since the fix CL are still in review process, we're try to manually uprev the Chrome version 58.0.2997.0 for Chrome OS.
 

Comment 1 by x...@chromium.org, Jan 30 2017

Cc: slavamn@chromium.org akes...@chromium.org
The failure on falco PFQ should be a flake since the DeviceNotPinable failure was also around last week and we did have successful PFQ occasionally, see https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq?numbuilds=100.

+cc deputy akeshet@ and sheriffs slavamn@

Comment 2 by leecy@chromium.org, Jan 30 2017

Cc: leecy@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Jan 31 2017

Project Member

Comment 4 by bugdroid1@chromium.org, Jan 31 2017

Project Member

Comment 5 by bugdroid1@chromium.org, Jan 31 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/fb30a30158172099260a9d28556daebbabfa574f

commit fb30a30158172099260a9d28556daebbabfa574f
Author: xdai <xdai@chromium.org>
Date: Mon Jan 30 19:45:20 2017

Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1292672, build_number 3906

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.2997.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2997.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2997.0_rc-r1.afdo'} and updated Manifest"

"Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.2997.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.2997.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.2997.0_rc-r1.afdo'} and updated Manifest"

Marking latest_release for chromium-source ebuild with version 58.0.2997.0 as stable.

Marking latest_release for chromeos-chrome ebuild with version 58.0.2997.0 as stable.

BUG= chromium:686840 
TEST=None
CQ-DEPEND=*I08b75059c3688db9d9c4b73e1fd6781d1edd384b

Change-Id: I5d2b3611c4de39ebc0b1ceab8c9db7c3012acff5
Reviewed-on: https://chromium-review.googlesource.com/434758
Trybot-Ready: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Dominik Behr <dbehr@chromium.org>
Tested-by: Dominik Behr <dbehr@chromium.org>
Tested-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>

[rename] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos-base/chromeos-chrome/chromeos-chrome-58.0.2997.0_rc-r1.ebuild
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[rename] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos-base/chromium-source/chromium-source-58.0.2997.0_rc-r1.ebuild
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos-base/chromeos-chrome/Manifest
[modify] https://crrev.com/fb30a30158172099260a9d28556daebbabfa574f/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf

Comment 6 by x...@chromium.org, Jan 31 2017

Status: Fixed (was: Assigned)
In GoldenEye, under M58 builds (https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?milestone=58#%2F), there are two builds using 58.0.2997.0. So the manual uprev should have succeeded.

Comment 7 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 8 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 9 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61
Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!

Sign in to add a comment