From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106360 invoked by alias); 9 Aug 2019 16:12:25 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 106350 invoked by uid 89); 9 Aug 2019 16:12:25 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-9.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: rgout03.bt.lon5.cpcloud.co.uk Received: from rgout0305.bt.lon5.cpcloud.co.uk (HELO rgout03.bt.lon5.cpcloud.co.uk) (65.20.0.211) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 09 Aug 2019 16:12:23 +0000 X-OWM-Source-IP: 31.51.206.190 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN Received: from [192.168.1.102] (31.51.206.190) by rgout03.bt.lon5.cpcloud.co.uk (9.0.019.26-1) (authenticated as jonturney@btinternet.com) id 5D42B519007CB321 for cygwin-apps@cygwin.com; Fri, 9 Aug 2019 17:12:20 +0100 Subject: Re: git repositories for cygwin packaging - please test To: "cygwin-apps@cygwin.com" References: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk> <3paoke5p1iivphkr77dsj1hf14sb9cclk5@4ax.com> <3329d1d4-7e2a-a95e-0764-f539b41786a9@cornell.edu> From: Jon Turney Message-ID: <7cfb3f27-a757-565d-5bdb-974a8f105184@dronecode.org.uk> Date: Fri, 09 Aug 2019 16:12:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <3329d1d4-7e2a-a95e-0764-f539b41786a9@cornell.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2019-08/txt/msg00022.txt.bz2 On 08/08/2019 18:09, Ken Brown wrote: > On 8/8/2019 10:04 AM, Andrew Schulman via cygwin-apps wrote: >>> >>> These repositories are lazily created on the first push. >> >> In my testing, git push hangs on the first push, after "Initialized empty >> git repositories". After I interrupt, it finishes normally. Maybe a >> misconfiguration on my end. > > I'm seeing something like this too now, though I didn't when I first tested. In > my case it doesn't finish normally after the interrupt; I have to do a second > git push, which then works. > Thanks for reporting this problem. I need to look into this some more, but this looks like push is getting stuck due to creating the repo taking an unusually long time (perhaps due to lock contention with someone else creating a repo...).