From: Mikael Morin <morin-mikael@orange.fr>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc@gcc.gnu.org, Frank Eigler <fche@redhat.com>
Subject: Re: gcc git locked out for hours second day in a row
Date: Wed, 12 Jun 2024 16:53:38 +0200 [thread overview]
Message-ID: <e25c2242-00d5-4fe9-a819-731da8a75a52@orange.fr> (raw)
In-Reply-To: <7bd1692d-f3f3-4ccc-a9d0-45123323fc9f@arm.com>
Le 12/06/2024 à 16:34, Richard Earnshaw (lists) a écrit :
> On 12/06/2024 14:23, Mikael Morin via Gcc wrote:
>> Le 12/06/2024 à 14:58, Jonathan Wakely a écrit :
>>> On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc <gcc@gcc.gnu.org> wrote:
>>>>
>>>> Le 12/06/2024 à 13:48, Jakub Jelinek a écrit :
>>>>> Hi!
>>>>>
>>>>> Yesterday the gcc git repository was locked for 3 hours
>>>>> locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167)
>>>>> 78:06 python hooks/update.py refs/users/mikael/tags/fortran-dev_merges/r10-1545 0000000000000000000000000000000000000000 c2f9fe1d8111b9671bf0aa8362446516fd942f1d
>>>>> process until overseers killed it but today we have the same
>>>>> situation for 3 ours and counting again:
>>>>> locked by user mikael at 2024-06-12 08:35:48.137564 (pid = 2219652)
>>>>> 78:06 python hooks/update.py refs/users/mikael/tags/toto 0000000000000000000000000000000000000000 cca005166dba2cefeb51afac3ea629b3972acea3
>>>>>
>>>>> It is possible we have some bug in the git hook scripts, but it would
>>>>> be helpful trying to understand what exactly you're trying to commit
>>>>> and why nobody else (at least to my knowledge) has similarly stuck commits.
>>>>>
>>>>> The effect is that nobody can push anything else to gcc git repo
>>>>> for hours.
>>>>>
>>>>> Jakub
>>>>>
>>>> Yes, sorry for the inconvenience.
>>>> I tried pushing a series of tags labeling merge points between the
>>>> fortran-dev branch and recent years master.
>>>
>>> Just pushing tags should not cause a problem, assuming all the commits
>>> being tagged already exist. What exactly are you pushing?
>>>
>> Well, the individual commits to be merged do exist, but the merge points don't and they are what I'm trying to push.
>>
>> To be clear, the branch hasn't seen any update for years, and I'm trying to reapply what happened on trunk since, in a step-wise manner. With 300 merges I'm summing up 60000 commits of history.
>>
>>>
>>>> The number of merge points is a bit high (329) but I expected it to be a
>>>> manageable number. I tried again today with just the most recent merge
>>>> point, but it got stuck again. I should try with the oldest one, but
>>>> I'm afraid locking the repository again.
>>>>
>>>> I waited for the push to finish for say one hour before killing it
>>>> yesterday, and no more than 15 minutes today. Unfortunately, killing
>>>> the process doesn't seem to unlock things on the server side.
>>>>
>>>> It may be a misconfiguration on my side, but I have never had this
>>>> problem before.
>>>>
>>>> Sorry again.
>>>>
>>>>
>>
>
> Perhaps you could create a mirror version of the repo and do some experiments locally on that to identify where the bottle-neck is coming from?
>
Not sure where to start for that.Are the hooks published somewhere?
next prev parent reply other threads:[~2024-06-12 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 11:48 Jakub Jelinek
2024-06-12 12:14 ` Mark Wielaard
2024-06-12 12:57 ` Mikael Morin
2024-06-12 12:55 ` Mikael Morin
2024-06-12 12:58 ` Jonathan Wakely
2024-06-12 13:23 ` Mikael Morin
2024-06-12 14:34 ` Richard Earnshaw (lists)
2024-06-12 14:53 ` Mikael Morin [this message]
2024-06-12 14:57 ` Jakub Jelinek
2024-06-23 20:22 ` Mikael Morin
2024-06-12 15:55 ` Jonathan Wakely
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=e25c2242-00d5-4fe9-a819-731da8a75a52@orange.fr \
--to=morin-mikael@orange.fr \
--cc=Richard.Earnshaw@arm.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely.gcc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).