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

Issue 655800 link

Starred by 1 user
Status: Verified
Owner:
█ lpique@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
█ keta...@chromium.org
steve...@chromium.org
█ dbehr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Manually uprev Chrome to 56.8891.0.0 for Chrome OS

Project Member Reported by lpique@chromium.org, Oct 13 2016 
Due to a series of infrastructure issues (primarily  issue 652207  affecting falco-chrome-pfq) we have not had a Chrome uprev since Thursday October 6.

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

only had one failing slave, tricky:
https://uberchromegw.corp.google.com/i/chromeos/builders/tricky-chrome-pfq/builds/2448

and the failure was due to a provision failure, seemingly caused by a hardware/microcode error (issue 655758).

Comment 1 by lpique@chromium.org, Oct 13 2016

Labels: Build-PFQ-Failures

Comment 2 by lpique@chromium.org, Oct 13 2016

Components: Infra>Client>ChromeOS
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 14 2016 

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

commit e48db37af038849d4c22e4b99f0bff348df10fc7
Author: Lloyd Pique <lpique@google.com>
Date: Thu Oct 13 21:02:55 2016

Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1109157, build_number 3470

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

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

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

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

BUG= chromium:655800 
TEST=None
CQ-DEPEND=*Id8528da614c2b9dbd47010963f3a86ed48199c12

Change-Id: I1e3aebb585f6c6b484bac68e611400fb4fd75d3c
Reviewed-on: https://chromium-review.googlesource.com/398243
Commit-Ready: Ben Cheng <bccheng@chromium.org>
Tested-by: Lloyd Pique <lpique@google.com>
Tested-by: Ben Cheng <bccheng@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>

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

Comment 4 by bugdroid1@chromium.org, Oct 14 2016 

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

commit fde52c9a26bc95df29461983cf1ee04459b4e415
Author: Lloyd Pique <lpique@google.com>
Date: Thu Oct 13 21:02:56 2016

Comment 5 by lpique@chromium.org, Oct 14 2016

Status: Fixed (was: Started)

Comment 6 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 7 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

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

Labels: VerifyIn-59

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

Labels: VerifyIn-60

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

Labels: VerifyIn-61

Comment 11 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