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

Issue 839235 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Manually rev Chrome to 68.0.3417.0

Project Member Reported by bhthompson@google.com, May 3 2018

Issue description

The Chrome PFQ runs for 68.0.3417.0 have fully passed HWTest on a run, in that run the only failures were purple builders that appear to have been interrupted.

The builders that were interrupted appear to have passed on other prior runs with this same Chrome, so we have some confidence this Chrome is good. As such I plan to mark https://luci-milo.appspot.com/buildbot/chromeos/master-chromium-pfq/6337 (2535442) as good via `cros uprevchrome --pfq-build 2535442`.
 
Project Member

Comment 1 by bugdroid1@chromium.org, May 3 2018

Project Member

Comment 2 by bugdroid1@chromium.org, May 3 2018

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

commit 723d6cfaacf36915b5492d268a0dc18d3aaaa9dc
Author: Bernie Thompson <bhthompson@google.com>
Date: Thu May 03 04:47:50 2018

Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 2535442, build_number 6337

Marking set of ebuilds as stable

Update PFQ config dump

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

Update profiles and manifests for Chrome.

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

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

BUG= 839235 
TEST=None
CQ-DEPEND=*Ib8c94d27dc696056c236dae53ac1cdc5dcc269f8

Change-Id: I58588022024b147380e7735d191119575a83511e
Reviewed-on: https://chromium-review.googlesource.com/1041571
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>

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

Status: Fixed (was: Untriaged)
If any problems are noted with this, please let me know and I will do all I can to resolve them.

Apologies for the late change, we need this to get 68 dev out this week.

Comment 4 by warx@chromium.org, May 3 2018

Cc: minch@chromium.org
I agreed with manual uprev. The only issue yesterday was issue 839028.

Sign in to add a comment