15

I have been trying to clone the aosp repo, it worked fine last week but hasn't been for the last two days. I narrowed it down to the deqp dependecy. With the however I got multiple errors but always resulting in "fatal: fetch-pack: invalid index-pack output". Last try resulted in this:

   /run/me/j/d/a/deqp    master  git config http.postBuffer 524288000
   /run/me/j/d/a/deqp    master  git fetch --unshallow               ✔ 
remote: Finding sources: 100% (126764/126764)
remote: Total 126764 (delta 86667), reused 126714 (delta 86667)
Receiving objects: 100% (126764/126764), 2.33 GiB | 6.12 MiB/s, done.
error: inflate: data stream error (incorrect data check)
fatal: serious inflate inconsistency
fatal: fetch-pack: invalid index-pack output

What could be the problem?

koniety
  • 153
  • 1
  • 1
  • 7
  • Does this answer your question? [fatal: early EOF fatal: index-pack failed](https://stackoverflow.com/questions/21277806/fatal-early-eof-fatal-index-pack-failed) – SwissCodeMen Dec 06 '21 at 21:59
  • 1
    No sadly it does not. I tried that already. The final result remains the same: "fatal: fetch-pack: invalid index-pack output" – koniety Dec 06 '21 at 22:05
  • 2
    This is usually caused by a proxy (https redirector) that has a bug and corrupts your data. You can try using ssh, if that's available, or remove the "security appliance" that's making your network super-secure by making it not work. :-) – torek Dec 07 '21 at 03:51
  • Just as an addition, I haven't found a solution to the problem as it just went away a couple of days later. For anyone still looking at this question, a lot of the solutions are pretty good. – koniety Sep 24 '22 at 10:32
  • I hit this in a CircleCI Orb...Upgrading the docker container size solved it for me, using the `resource_class` attribute. – Richard Jan 31 '23 at 13:13

5 Answers5

10

I also encountered this problem on macOS Big Sur 11.6.1, and I run ulimit -n unlimited and ulimit -f unlimited to resolve this. Increase the value of packedGitLimit or packedGitWindowSize and packSizeLimit on gitconfig did not work for me.

SmartKeyerror
  • 269
  • 1
  • 4
  • 8
4

If the proj is too big, try using --depth=1 to solve.

Gino Mempin
  • 25,369
  • 29
  • 96
  • 135
Teanix
  • 41
  • 1
3

Try to run the following:

git config pack.windowMemory 10m

git config pack.packSizeLimit 20m

then retry the git clone.

iammtander
  • 111
  • 1
  • 2
2

This solved my problem.

git pull --depth=1 {repo} {branch}
Gino Mempin
  • 25,369
  • 29
  • 96
  • 135
Nurul Huda
  • 21
  • 2
0

In my case, this is works

git reset --hard
git clean -dfx
git fetch --all --depth 1
Isma Rekathakusuma
  • 856
  • 12
  • 18