Missing Git commit hash in remote "llvm-project" repository?

[Kevin Marshall]

I'm trying to help a teammate checkout and build Chrome from a new repo, and we're getting stuck on this error:

Error: Command 'git checkout --quiet 9a39e428d018b723d7d187181fd08908b1cb6bd0' returned non-zero exit status 128 in /usr/local/google/home/lethalantidote/blimp/src/buildtools/third_party/libc++abi/trunk
fatal: reference is not a tree: 9a39e428d018b723d7d187181fd08908b1cb6bd0

I checked out buildtools/third_party/libc++abi/trunk and inspected the Git log. I couldn't find 9a39e42... anywhere. So I did a git clone of the llvm-project directory, and couldn't find 9a39e42 there, either.

On my personal workstation, which builds fine, I can see the commit hash in the Git log.

I get a 404 if I attempt to access the commit info via the Web interface: https://chromium.googlesource.com/chromium/llvm-project/libcxxabi/+/9a39e428d018b723d7d187181fd08908b1cb6bd0

BUT, I can see if if I view the Google cached version: https://webcache.googleusercontent.com/search?q=cache:FcWEv_xPmkQJ:https://chromium.googlesource.com/chromium/llvm-project/libcxxabi/%2B/9a39e428d018b723d7d187181fd08908b1cb6bd0+&cd=1&hl=en&ct=clnk&gl=us

which makes me think that there might be data loss in the Git repo? Very puzzling.

Kevin

[Nevyn Bengtsson]

Hey Kevin et al,

I'm having the same problem when trying to `gclient sync` and build webrtc for iOS. Running it yields:

```fatal: Needed a single revision

Does not point to a valid commit: 9a39e428d018b723d7d187181fd08908b1cb6bd0```

... among all the other stuff it's printing.

A googling of that ref gives me someone's log file that says that `9a39e42` is "9a39e42 Add new tests for throwing incomplete pointer types". Googling the commit message tells me that this commit is actually called `0edb61e`: https://chromium.googlesource.com/external/llvm.org/libcxxabi/+/0edb61e2e581758fc4cd4cd09fc588b3fc91a653

Has there been a recent forcepush or something? I could swear that this script worked earlier today, but I've been struggling (for maybe the two-three past hours?) to get this to sync and build. (tbh I've tried to get webrtc to build for a week now, but that's another matter...)

Thanks.

[s0nicyouth]

Getting the same message since this morning when trying to build Chromium:

________ running 'git -c core.deltaBaseCacheLimit=512m fetch origin --verb

d_party\libc++abi\trunk'

[0:00:18] From https://chromium.googlesource.com/chromium/llvm-project/lib

[0:00:18]  = [up to date]      master     -> origin/master

[0:00:18]  = [up to date]      release_32 -> origin/release_32

[0:00:18]  = [up to date]      release_36 -> origin/release_36

[0:00:18]  = [up to date]      release_37 -> origin/release_37

[0:00:18]  = [up to date]      release_38 -> origin/release_38

[0:00:18] Attempting rebase onto 9a39e428d018b723d7d187181fd08908b1cb6bd0.

[0:00:19]

[0:00:19] Rebase produced error output:

fatal: Needed a single revision

Does not point to a valid commit: 9a39e428d018b723d7d187181fd08908b1cb6bd0

Looks like someone did something to repo(forcepushed?)

[Nico Weber]

There's a bug for this as well: https://crbug.com/615278

As far as I know, nothing has changed here. We haven't updated libc++ in months, and the DEPS file in buildtools hasn't changed since January. The most obvious explanation is that someone force-pushed to the git repo and broke commits. Other than that, buildtools is a recursive DEPS file, and there's been some talk about changing how those work, but no recent commits in depot_tools look like something like that happened.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Michael Moss]

It looks like this is due to changing our repos from mirroring our old svn.chromium mirrors, to mirroring the upstream git repo directly. agable is working on pushing the old refs back to the repo.

[Aaron Gable]

Thanks everyone for bringing this to our attention. Further updates from me will take place on the bug, and I'll post another short message here when I believe this to be resolved.

[Paweł Hajdan, Jr.]

+infra-dev

[Aaron Gable]

This issue should now be resolved. Thanks everyone for your patience, and sorry for the breakage.