mirror of
https://github.com/renovatebot/renovate.git
synced 2026-11-02 10:33:39 +00:00
65be1c5cee
We periodically see test flakiness in the `git` functionality, where we're trying to clean up our temporary directories, and see i.e. [0]: ``` FAIL lib/util/git/index.spec.ts > util/git/index > ... Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-2701-SIDrNnhWZmc7/.git/objects' ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/4]⎯ FAIL lib/util/git/index.spec.ts > util/git/index > ... Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-2701-8p6HvIMqwS4k/.git/info' ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/4]⎯ FAIL lib/util/git/index.spec.ts > util/git/index > ... Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-2701-Q6gACVUhHYu1/.git/objects/pack' ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/4]⎯ FAIL lib/util/git/index.spec.ts > util/git/index > ... Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-2701-5VelWdq8M1Iy/.git/objects/pack' ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/4]⎯ ``` Investigating this with Claude Sonnet, it appears that this /could be/ down to Git's automated garbage collection processes. The infrequency of the failures makes this less straightforward to investigate the issue, but it seems like this may be the likely culprit. We had enabled this on `base` and `origin` repos, but never the `local` client which runs against `tmpDir`. We can make sure that this is applied, and this should reduce the flakiness. Co-authored-by: Claude Sonnet 5 <jamie.tanna+claude-code@mend.io> [0]: https://github.com/renovatebot/renovate/actions/runs/32008122699/job/95322113612