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

Issue 838248 link

Starred by 2 users
Status: WontFix
Owner:
beccahughes@chromium.org
Closed: Jul 3
Cc:
█ shenghua...@chromium.org
jbudorick@chromium.org
vadimsh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

gclient sync does not work on M67 release branch

Project Member Reported by beccahughes@chromium.org, Apr 30 2018 
OS: Linux

I am trying to build the M67 release branch using these instructions: https://www.chromium.org/developers/how-tos/get-the-code/working-with-release-branches

gclient sync is crashing with the following error:

Syncing projects: 100% (229/229), done.                                                                                                                                                                       

________ running 'cipd ensure -log-level error -root /usr/local/google/home/beccahughes/chromium -ensure-file /tmp/tmpmk2ZeE.ensure' in '.'
[P152080 10:02:14.575 client.go:1300 E] cipd: failed to fetch chromium/third_party/android_sdk/public/tools:ff1b6f2de757c0968774089f866e5591f628b836 - package "chromium/third_party/android_sdk/public/tools" doesn't have instance "ff1b6f2de757c0968774089f866e5591f628b836"
[P152080 10:02:14.575 client.go:1431 E] Failed to install chromium/third_party/android_sdk/public/tools:ff1b6f2de757c0968774089f866e5591f628b836 - package "chromium/third_party/android_sdk/public/tools" doesn't have instance "ff1b6f2de757c0968774089f866e5591f628b836"
Error: failed to update packages, see the log.
Error: Command 'cipd ensure -log-level error -root /usr/local/google/home/beccahughes/chromium -ensure-file /tmp/tmpmk2ZeE.ensure' returned non-zero exit status 1

Comment 1 by vadimsh@chromium.org, May 4 2018

Cc: jbudorick@chromium.org shenghua...@chromium.org
Components: -Infra Infra>Platform>CIPD Infra>Client>Chrome
What exact chromium/src git revision are you checking out?

Is this reproducible? 

If it is, try removing chromium/src/.cipd/tagcache.db (or maybe just <gclient_solution_root>/.cipd/tagcache.db, I don't remember where exactly it is).

---

It appears the package instance ff1b6f2de757c0968774089f866e5591f628b836 existed, but doesn't exist anymore. Either someone deleted it, or it is a bug in the CIPD backend.

Resolution of CIPD version tags (like "version:26.1.1-cr0") to instance IDs is cached locally, since version tags are assumed to be immutable. If they are mutated (e.g. by completely deleting the package then creating it from scratch), stuff like this may happen.

Comment 2 by vadimsh@chromium.org, May 4 2018 

To be clear: removing .cipd/tagcache.db is a short term workaround. Long term we'll have tighter ACL around actions that break immutability of version labels, so this situation doesn't happen.

Comment 3 by sergeybe...@chromium.org, May 8 2018

Owner: beccahughes@chromium.org
Status: Assigned (was: Untriaged)
Assigning back to beccahughes@chromium.org to try suggestion in #c2. Please mark "Untriaged" if you need more help from us.

Comment 4 by beccahughes@chromium.org, Jul 3

Status: WontFix (was: Assigned)
►

Sign in to add a comment