New issue
Advanced search Search tips

Issue 789164 link

Starred by 1 user
Status: Archived
Owner:
xixuan@chromium.org
Closed: Dec 2017
Cc:
drinkcat@chromium.org
xhw...@chromium.org
hmchen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

ChromePFQ bots are marked as failures due to pinned chrome version

Project Member Reported by osh...@chromium.org, Nov 28 2017 
Example:

https://uberchromegw.corp.google.com/i/chromeos/builders/amd64-generic-chromium-pfq/builds/11004

17:26:23: INFO: RunCommand: cros_sdk -- emerge-amd64-generic -p --quiet '=chromeos-base/chromeos-chrome-64.0.3278.0_rc-r1'
17:26:29: ERROR: Cannot emerge-amd64-generic =chromeos-base/chromeos-chrome-64.0.3278.0_rc-r1
Is Chrome pinned to an older version?
17:26:29: ERROR: Chrome is pinned. Unpinning chrome and continuing build for chrome atom chromeos-base/chromeos-chrome-64.0.3278.0_rc-r1. This stage will be marked as failed to prevent an uprev.


While this isn't causing real issue, this makes it difficult to find the real issue, so we should resolve this asap.

Comment 1 by osh...@chromium.org, Nov 28 2017

Blockedon: 788925

Comment 2 by xixuan@chromium.org, Nov 28 2017 

chrome is unpinned. PFQ should be unblocked.

Comment 3 by drinkcat@chromium.org, Dec 1 2017

Blockedon: -788925
Status: Fixed (was: Assigned)

Comment 4 by dchan@google.com, Jul 30

Status: Archived (was: Fixed)
►

Sign in to add a comment