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

Issue 803549 link

Starred by 1 user
Status: WontFix
Owner:
derat@chromium.org
Closed: Jan 2018
Cc:
█ shuqianz@chromium.org
kcwu@chromium.org
phshah@chromium.org
wutao@chromium.org
sonnyrao@chromium.org
█ uekawa@chromium.org
la...@chromium.org
osh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Manually uprev Chrome to 65.0.3324.0_rc-r1 for Chrome OS

Project Member Reported by derat@chromium.org, Jan 18 2018 
Due to infrastructure issue 803239, we have not had a Chrome uprev since 
65.0.3322.0 on 2018-01-16 19:52.

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

only had this failing slave:
https://luci-milo.appspot.com/buildbot/chromeos/veyron_minnie-chrome-pfq/2386

and the failure was due to issue 803239.

https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-chrome-pfq/builds/2383 passed using Chrome 65.0.3324.0_rc-r1 (i.e. the same version).

Comment 1 by derat@chromium.org, Jan 18 2018 

I've sent https://crrev.com/i/549306 and https://crrev.com/c/874930 to the CQ, but given the state of the CQ over the last day or two (hopefully fixed now; see issue 803239), I'm not sure how long they'll take to go in.

Comment 2 by derat@chromium.org, Jan 18 2018 

Per discussion on crosoncall, I'm holding off on the uprev to see if the current run (http://uberchromegw/i/chromeos/builders/master-chromium-pfq/builds/5607) finally passes.

Comment 3 by derat@chromium.org, Jan 18 2018

Status: WontFix (was: Started)
http://uberchromegw/i/chromeos/builders/master-chromium-pfq/builds/5607 passed, so I think we should be at 65.0.3324.0 now without the need for a manual uprev.
►

Sign in to add a comment