From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
GIT Mailing-list <git@vger.kernel.org>,
Patrick Steinhardt <ps@pks.im>,
Adam Dinwoodie <adam@dinwoodie.org>
Subject: Re: v2.46.0-rc0 test failures on cygwin
Date: Wed, 17 Jul 2024 07:48:50 -0700 [thread overview]
Message-ID: <xmqq4j8o6pm5.fsf@gitster.g> (raw)
In-Reply-To: <20240717064241.GF547635@coredump.intra.peff.net> (Jeff King's message of "Wed, 17 Jul 2024 02:42:41 -0400")
Jeff King <peff@peff.net> writes:
> On Tue, Jul 16, 2024 at 08:45:48PM +0100, Ramsay Jones wrote:
>
>> error: could not link file '.git/ref_migration.sr9pEF/reftable' to '.git/reftable': Permission denied
>> migrated refs can be found at '.git/ref_migration.sr9pEF'
>> [...]
>> Now try to finish the migration by hand:
>>
>> $ mv .git/ref_migration.sr9pEF/reftable .git/reftable
>>
>> Hmm, note no error; of course, the mv command may well do much more than
>> the rename() library function, so they are not necessarily equivalent.
>
> This is a shot in the dark, but: could the problem be an open file that
> cannot be moved? If I run a "ref migrate" on my Linux system in the
> debugger and stop at move_files(), checking /proc/<pid>/fd shows an open
> descriptor for .git/ref_migration.WnJ8TS/reftable/tables.list.
Hmph, I wonder ifthat means the same test should be failing on
Windows, too?
next prev parent reply other threads:[~2024-07-17 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 19:45 v2.46.0-rc0 test failures on cygwin Ramsay Jones
2024-07-17 6:42 ` Jeff King
2024-07-17 14:48 ` Junio C Hamano [this message]
2024-07-17 18:10 ` Ramsay Jones
2024-07-17 18:05 ` Ramsay Jones
2024-07-18 0:57 ` Jeff King
2024-07-18 1:22 ` Ramsay Jones
2024-07-18 4:52 ` Junio C Hamano
2024-07-21 13:48 ` Adam Dinwoodie
2024-07-23 10:30 ` Patrick Steinhardt
2024-07-23 20:49 ` Jeff King
2024-07-23 12:31 ` [PATCH] refs: fix format migration on Cygwin Patrick Steinhardt
2024-07-23 19:29 ` Ramsay Jones
2024-07-23 20:13 ` Junio C Hamano
2024-07-23 20:52 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4j8o6pm5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=ramsay@ramsayjones.plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.