Bug 183392 – commit-queue failed with error: There are too many unreachable loose objects; run git prune to remove them

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: Tools / Tests

[Aakash Jain]

commit-queue failed in https://bugs.webkit.org/show_bug.cgi?id=183299

It seems to have landed the patch, but it shows that it failed.  https://webkit-queues.webkit.org/results/6833744


It's logs have following error:


Last 500 characters of output:
ls/ChangeLog
r229349 = c3710bd8a5d1173ab6b53e0d79ece83f5b3421d1 (refs/remotes/origin/master)
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

gc --auto: command returned error: 255

[Alexey Proskuryakov]

I saw it in another bug today, too.

[Aakash Jain]

Another similar failure in https://bugs.webkit.org/show_bug.cgi?id=183396  (https://webkit-queues.webkit.org/results/6835274)

[Aakash Jain]

This error is happening only on webkit-cq-02 machine. Logs on webkit-cq-01 and webkit-cq-03 doesn't have this error. I just manually run "git prune" on webkit-cq-02. Let's see if that helps.

[Alexey Proskuryakov]

This night, it happened on webkit-cq-01 in bug 183400.

[Aakash Jain]

Another one (webkit-cq-01): https://bugs.webkit.org/show_bug.cgi?id=183394#c4  (https://webkit-queues.webkit.org/results/6841309)

[Aakash Jain]

Observation: The issue didn't happened on webkit-cq-02 after I run "git prune" yesterday night. It started happening on webkit-cq-01.

[Aakash Jain]

Did following to fix/improve this:

1) Run "git prune" on all the webkit-cq-* machines. 

2) Configured following variables to have better git gc:

git config --global gc.reflogExpire 30    (defaults to 90 days)
git config --global gc.reflogExpireUnreachable 10  (defaults to 30 days)

Reference: https://git-scm.com/docs/git-gc#_configuration

3) Running "git gc --aggressive" currently.

[Aakash Jain]

Closing it as we haven't seen this issue again after doing configuration changes.