git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Exit code 255 after large clone (32-bit PowerPC)

From
EMEvan Miller <emmiller@gmail.com>
Date
Jul 26, 2021, 17:54 UTC
Message-ID
<D3C1583B-8CC8-434B-8AF5-B9827A7FD037@gmail.com>
What did you do before the bug happened? (Steps to reproduce your issue)

$ git clone -v git@github.com:macports/macports-ports.git Cloning into 'macports-ports'... remote: Enumerating objects: 1223319, done. remote: Counting objects: 100% (685/685), done. remote: Compressing objects: 100% (341/341), done. remote: Total 1223319 (delta 289), reused 608 (delta 252), pack-reused 1222634 Receiving objects: 100% (1223319/1223319), 244.46 MiB | 1.09 MiB/s, done. Connection to github.com closed by remote host. Resolving deltas: 100% (702052/702052), done.

What did you expect to happen? (Expected behavior)
A successful clone.
What happened instead? (Actual behavior)

$ echo $? 255 $ ls -a macports-ports/ . .. .git

What's different between what you expected and what actually happened?
Exit value was 255 instead of 0; no regular files (only .git files) are visible in the cloned directory.
Anything else you want to add:
Other repositories have cloned just fine; however, this repo is considerably larger than the successful cases.
This is a 32-bit PowerPC machine.

[System Info] git version: git version 2.32.0 cpu: Power no commit associated with this build sizeof-long: 4 sizeof-size_t: 4 shell-path: /bin/sh uname: Darwin 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh compiler info: gnuc: 4.2 libc info: no libc information available

Next: brian m. carlson
Message 1 of 9 in “Exit code 255 after large clone (32-bit PowerPC)”
  1. Evan MillerJul 26, 2021
  2. brian m. carlsonJul 26, 2021
  3. Evan MillerJul 26, 2021
  4. Ævar Arnfjörð BjarmasonJul 27, 2021
  5. brian m. carlsonJul 27, 2021
  6. Junio C HamanoJul 27, 2021
  7. Evan MillerJul 27, 2021
  8. Jeff KingJul 27, 2021
  9. Evan MillerJul 27, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.