`fetch chromium` fails with `fatal: fetch-pack: invalid index-pack output`

[Kyle McNally]

Hello all,

I'm building chromium for the first time, but having some difficulty running fetch. I've tried it on a few different environments (arch, amazonlinux2), using two different physical locations (different internet connections) and they are all failing at the same point. I'm running `fetch --nohooks --no-history chromium` and when it comes to 

git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress https://chromium.googlesource.com/external/github.com/KhronosGroup/VK-GL-CTS --template=/home/kyle/chromium/test/depot_tools/src/third_party/angle/third_party/VK-GL-CTS/_gclient_gittmp_srcn_znl7rr /home/kyle/chromium/test/depot_tools/src/third_party/angle/third_party/VK-GL-CTS/_gclient_src_64d1niel

it fails with `[0:25:27] fatal: fetch-pack: invalid index-pack output`

I've also tried running that command in just normal bash and Git is giving me the same output, nothing I've tried is working. Does anyone have any advice?

Thanks!

[Stefan Zager]

I'm not sure how well-supported --no-history is, I'd suggest trying without that flag. If it succeeds, please file a bug about --no-history.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/71b2e044-3a6c-4728-97ee-4170b16a90acn%40chromium.org.

[Kyle McNally]

Thanks for the tip. It turned out to be related to the VM I was building in. I had dynamic memory turned on my hypervisor, but the VM was not using dynamic memory and was statically set to use 2 gigs, so it was running out of ram. Setting the VM to use 32 gigs enabled fetch to succeed.

--

Kyle McNally about.me/kylemcnally