Re: [PATCH] perf: work around the tested repo having an index.lock
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 4, 2017, 00:51 UTC
- Message-ID
- <xmqq60gcwp6x.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <xmqqefv0wrj7.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
> Perhaps run "fsck" and "status" immediately after copying to make > sure they succeed, or something like that?
Hmph, this is me half-being silly, as this "copying an existing one" is meant for testing Git with a large repository, and having to run fsck may add meaningful overhead in addition to the actual copying in the set-up procedure. I do not offhand think of a good solution.