Git memory issue with armv7 fanned containers
Open
Nobody has claimed this yet.
incident
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
08:51:12 + ssh-agent sh -c 'ssh-add **** && git fetch --no-tags binary_tmp@147.75.72.255:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-c7f8b1629123065c20362ca5c2be0552405fbc4a-binary-pi1p/cc-armv7:refs/remotes/jenkins_tmp'
08:51:12 Identity added: **** (****)
08:51:49 fatal: packfile .git/objects/pack/pack-dd8f2842296180e0ffb6376cb0696c662e80f52a.pack cannot be mapped: Cannot allocate memory
08:51:49 fatal: index-pack failed
The .git folder takes quite a bit of space:
$ du -sh .git
324G .git
I'm not sure how to resolve this other than by wiping the workspace. How can we prevent the repository from growing in the future?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked node-test-binary-armv7l console log and inspect the git fetch that fails in the armv7l workspace. Check how the CI job manages its existing .git directory and whether repeated fetches account for the reported 324G size. Done means identifying a reproducible cause and documenting or implementing a way to prevent unbounded workspace growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- build-system, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100