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

Issue 808097 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

src/third_party/gles1_conform sync error

Project Member Reported by robliao@chromium.org, Feb 1 2018

Issue description

I just ran into this updating to origin/lkcr. 
Assigning per discussion thread.

E:\>gclient sync -D
Syncing projects: 100% (137/137) src/v8

src/third_party/gles1_conform (ERROR)
----------------------------------------
[0:00:09] Started.
[0:00:09]

________ running 'git -c core.deltaBaseCacheLimit=512m clone --no-checkout --progress https://chrome-internal.googlesource.com/angle/es-cts.git E:\src\third_party\_gclient_gles1_conform_wnw4vp' in 'E:\'
[0:00:09] Cloning into 'E:\src\third_party\_gclient_gles1_conform_wnw4vp'...
[0:00:11] _____ Conflicting directory found in E:\src\third_party\gles1_conform. Moving to E:\_bad_scm\src\third_party\gles1_conform7be1fo.
[0:00:11]

________ running 'git -c core.deltaBaseCacheLimit=512m clone --no-checkout --progress https://chrome-internal.googlesource.com/angle/es-cts.git E:\src\third_party\_gclient_gles1_conform_sdytdq' in 'E:\'
[0:00:11] Cloning into 'E:\src\third_party\_gclient_gles1_conform_sdytdq'...
----------------------------------------
Error: Command 'git rev-parse --verify FETCH_HEAD' returned non-zero exit status 128 in E:\src\third_party\gles1_conform
fatal: Needed a single revision



Warnings:
Conflicting directory E:\src\third_party\gles1_conform moved to E:\_bad_scm\src\third_party\gles1_conform7be1fo.

 
I'm hitting the same issue. Any workarounds?

Project Member

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

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/src-internal.git/+/49060e2c5247d64dce3f93c309d5bfb705a75872

commit 49060e2c5247d64dce3f93c309d5bfb705a75872
Author: Robert Liao <robliao@google.com>
Date: Thu Feb 01 18:53:32 2018

Cc: geoffl...@chromium.org
Owner: robliao@chromium.org
Status: Fixed (was: Assigned)
Sync is now succeeding for me.
Project Member

Comment 6 by bugdroid1@chromium.org, Feb 1 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5c7b94ab2823f7772d396f2f100a22f219b5d11d

commit 5c7b94ab2823f7772d396f2f100a22f219b5d11d
Author: src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Feb 01 20:06:09 2018

Roll src-internal/ a7522c8b7..339865817 (1 commit)

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a7522c8b7424..339865817c04

$ git log a7522c8b7..339865817 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src-internal
BUG= 808097 


The AutoRoll server is located here: https://src-internal-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=mmoss@chromium.org

Change-Id: Ib556065f43bc9363e2cc978dccff7273cc6c8d52
Reviewed-on: https://chromium-review.googlesource.com/897990
Reviewed-by: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533791}
[modify] https://crrev.com/5c7b94ab2823f7772d396f2f100a22f219b5d11d/DEPS

Status: Assigned (was: Fixed)
Failing for me again just now.
Cc: -geoffl...@chromium.org
Owner: geoffl...@chromium.org
@grunell: Please delete the src/third_party/gles1_conform folder and try again.  The permissions have been fixed but if you tried to sync when they were broken the repository gets into a bad state.
Status: Fixed (was: Assigned)
Ah, sure, it works now.

Sign in to add a comment