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

Issue 737205 link

Starred by 1 user
Status: Verified
Owner:
kaznacheev@chromium.org
Closed: Jul 2017
Cc:
█ keta...@chromium.org
jen...@chromium.org
steve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Manually uprev Chrome to XX.YYYY.0.0 for Chrome OS

Project Member Reported by kaznacheev@chromium.org, Jun 27 2017 
Due to a series of infrastructure issues, we have not had a Chrome uprev since #4515 (Jun 22 2017)

This PFQ run: 
https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/4537

only had these failing slaves: 
https://uberchromegw.corp.google.com/i/chromeos/builders/caroline-chrome-pfq/builds/143

which failing on VMTests which it should not be running (according to stevenjb@)
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 27 2017 

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

commit d3b9b9352673e13603383c0347c857b8ddf5f8fe
Author: Vladislav Kaznacheev <kaznacheev@google.com>
Date: Tue Jun 27 19:42:50 2017

Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1623199, build_number 4537

Marking set of ebuilds as stable

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

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

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

BUG= chromium:737205 
TEST=None
CQ-DEPEND=*I804ced4539d7382004793ae0ed4b27dd9732f097

Change-Id: I025c38f74671d3e0a0c6965df0a0bc6e246f607f
Reviewed-on: https://chromium-review.googlesource.com/549988
Tested-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>

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

Comment 2 by bugdroid1@chromium.org, Jun 27 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-partner-overlay/+/5276d25a8d360dfe6561e3b05c8498968be3131f

commit 5276d25a8d360dfe6561e3b05c8498968be3131f
Author: Vladislav Kaznacheev <kaznacheev@google.com>
Date: Tue Jun 27 19:42:43 2017

Comment 3 by kaznacheev@chromium.org, Jul 14 2017

Status: Fixed (was: Untriaged)

Comment 4 by abod...@chromium.org, Aug 3 2017

Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!
►

Sign in to add a comment