New issue
Advanced search Search tips

Issue 866262 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 700813



Sign in to add a comment

recover 3f7d76be9f572d8fdf512f4e2085109bc32a6128 in external/leveldb

Project Member Reported by vapier@chromium.org, Jul 21

Issue description

old CrOS factory branches are running into the same problem noted in this Chromium thread:
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/usLyeZynBYQ

basically, https://chromium.googlesource.com/external/leveldb/ used to have the commit 3f77584eb3f9754bbb7079070873ece3f30a1e6b, but at some point it was deleted (probably upstream), and then our automatic syncing logic deleted it from our repo as well.

it seems that ref still exists in an AOSP repo though:
  https://android.googlesource.com/platform/external/chromium_org/third_party/leveldatabase/src/+/3f77584eb3f9754bbb7079070873ece3f30a1e6b

ironically, it looks like ASOP was mirroring our mirror of leveldb ;).

can someone with admin privs pull in 3f77584eb3f9754bbb7079070873ece3f30a1e6b from AOSP to our external/leveldb and then give it a custom branch name that won't get it deleted automatically ?  name it like "backup/chromium/<crbug#>" or something.
 
Blocking: 700813
Owner: iannucci@chromium.org
Status: Started (was: Unconfirmed)
gclient sync only pulls tags & refs/heads/* (afaict), so this doesn't help default syncing logic.  could we use refs/heads/backup/ instead of refs/backup/ ?  or some namespaced tags ?
Status: Unconfirmed (was: Fixed)
ping ...
Owner: iannu...@google.com
Missed this ping (I believe I was out).

I don't believe it's possible to push something into refs/heads/* because they're currently being mirrored to with a gob config. I could stop mirroring all refs and only mirror refs/heads/master and then I could push to refs/heads/<not_master>

Gclient sync doesn't, by default, pull tags either, afaik.
The forum thread you link to was from 2016. Is there an instance of this happening recently?
Owner: vapier@chromium.org
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment