起初我们认为 gitshallow 可以解决这个问题。然而我们仍然看到了问题。它是间歇性的，并且也发生在没有分支和标签的存储库上。在 git fetch 期间在 Jenkins 构建上注意到的错误。在 git trace 或 git debug 中没有看到任何明显的东西。
关于如何解决这个问题有什么想法吗？
22:41:16 stdout:
22:41:16 stderr: remote: Enumerating objects: 781948, done.
22:41:16 remote: Counting objects: 0% (1/8931)
remote: Counting objects: 1% (90/8931)
remote: Counting objects: 2% (179/8931)
remote: Counting objects: 3% (268/8931)
remote: Counting objects: 4% (358/8931)
remote: Counting objects: 5% (447/8931)
remote: Counting objects: 96% (8574/8931)
remote: Counting objects: 97% (8664/8931)
remote: Counting objects: 98% (8753/8931)
remote: Counting objects: 99% (8842/8931)
remote: Counting objects: 100% (8931/8931)
remote: Counting objects: 100% (8931/8931), done.
22:41:16 remote: Compressing objects: 0% (1/2514)
remote: Compressing objects: 1% (26/2514)
remote: Compressing objects: 2% (51/2514)
remote: Compressing objects: 3% (76/2514)
remote: Compressing objects: 4% (101/2514)
remote: Compressing objects: 5% (126/2514)
remote: Compressing objects: 6% (151/2514)
remote: Compressing objects: 7% (176/2514)
remote: Compressing objects: 8% (202/2514)
remote: Compressing objects: 9% (227/2514)
remote: Compressing objects: 10% (252/2514)
remote: Compressing objects: 11% (277/2514)
remote: Compressing objects: 12% (302/2514)
remote: Compressing objects: 13% (327/2514)
remote: Compressing objects: 14% (352/2514)
remote: Compressing objects: 15% (378/2514)
remote: Compressing objects: 71% (1785/2514)
remote: Compressing objects: 72% (1811/2514)
remote: Compressing objects: 73% (1836/2514)
remote: Compressing objects: 74% (1861/2514)
remote: Compressing objects: 75% (1886/2514)
remote: Compressing objects: 76% (1911/2514)
remote: Compressing objects: 77% (1936/2514)
remote: Compressing objects: 78% (1961/2514)
remote: Compressing objects: 79% (1987/2514)
remote: Compressing objects: 97% (2439/2514)
remote: Compressing objects: 98% (2464/2514)
remote: Compressing objects: 99% (2489/2514)
remote: Compressing objects: 100% (2514/2514)
remote: Compressing objects: 100% (2514/2514), done.
22:41:16 Receiving objects: 0% (1/781948)
Receiving objects: 0% (1290/781948), 164.01 KiB | 157.00 KiB/s
Receiving objects: 0% (2623/781948), 332.01 KiB | 161.00 KiB/s
Receiving objects: 0% (3914/781948), 420.01 KiB | 161.00 KiB/s
Receiving objects: 68% (533555/781948), 101.66 MiB | 146.00 KiB/s
error: index-pack died of signal 15
22:41:16 fatal: index-pack failed
22:41:16 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2734)
22:41:16 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2111)
22:41:16 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:87)
22:41:16 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:623)
22:41:16 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:852)
22:41:16 at
最佳答案
信号 15 是 SIGTERM。有些东西要求您的进程正常退出(与 SIGKILL (9) 相反，后者更为激烈)。
您需要弄清楚该信号来自哪里。也许您已经根据系统知识进行了猜测，在这种情况下，您可以通过将 strace 附加到嫌疑人来确认。否则，https://stackoverflow.com/a/62434615/4811803可以帮助您找到罪魁祸首。
关于git - 如何修复 Git 中的 'index-pack died of signal 15' 错误？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/76361653/