From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by sourceware.org (Postfix) with ESMTPS id 06FC9388204B for ; Wed, 12 Jun 2024 12:58:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 06FC9388204B Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 06FC9388204B Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::52f ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1718197141; cv=none; b=FVT0P8NluxwmkWqulsd0Ir1nyZVa/paH8hki53vW3nGV4H/UdsmCHz8xvI5XozfatzJSNdnghalQA56lB4NuLNAFGA4h5PN0UbwgkHqQRkVVJwBcH6TV0tXn8iGhxsI3Px9hRAZ64JI2Ypp4Cgr9nI40mHenHxOmpQkumvYuf0Q= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1718197141; c=relaxed/simple; bh=Ifj8/FEkScMIqz+6ghb2E2Vy4IQQRd1rV+VzQJMem8M=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=P4bPv7SbHBuQQTE37NDrWaUks+rMUSWqHobiIVImEhjRy0vR1H00WsSDyo6JSOh/4BUGi/6HF8V/34f5K3rE39snafmasu5Qp2ogOicv5ydjv9aZ3zAbCduql8lKps6kNX8bh8NpG0wTJDr+6HJQP12bn62Wg3zc7jbG2l69PJg= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-57c7ec8f1fcso4633831a12.0 for ; Wed, 12 Jun 2024 05:58:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718197137; x=1718801937; darn=gcc.gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=4oJCJ7jo2fCr7SGtL9E2ReWrdggoD5rUEWu02VfB0F8=; b=K+wiaXiOprSdo2UawrysUGr/nxB1pRFhpBHotEkC4AKH1cohhc0W/LO3iDgug8XTH0 6PUMcHbj3xcgCf//K35cDnr/OKIo8Vplgh65iu1deGH4xjcP+3jokcnN+k2QFb9Kcle6 AhR9B2NwzFrNTalqRDrNahOoEQVv+IqWKA9hb2+8b4VO6fFwPS3yqRGJx2syOT3pLY+D rpPjNrfvE5F2tbHnqabgA29l+lfKxAshyztnuTEiluDaqzRZY7rc4KDRmr1TSL4iRMd6 BivQT6vY319O6xc4KftzvvtEeoQdkTNxqFCA2X4MDExvm8c4/+UsXf6LLbSso+rZQJPm AF3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718197137; x=1718801937; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4oJCJ7jo2fCr7SGtL9E2ReWrdggoD5rUEWu02VfB0F8=; b=Y46Ur6iCviFbeJNqSnHSBEFdXsC/Ya3L31Xy7J8bGyB13TCN/iY4GMOwF8wks0OMFY cu3JK5fjtelUDlZH56mxiNyRUT/DBWuF7hxEIAGZnleyWBxRtfomMZt4BCxZRZwXNssL d7T7a3U4dKaQJmPD47GCtGlm5ix4AFH/3dCu50F6G931BVer6S+2dXBV9JvvRNhTkzXr TkpbeRlaMd7/7OMA3RNjxniC1aOpnjCo5Rysxmfy6pcosBWzZ5aRITQjVLiXbbc7rvlT 6qgCrUxhMAWTMv24DO6N0ESznTsO0oGxACRjBLzAYmWP+bSuCaejbVmk99xS6MgG+3VI 9uWw== X-Forwarded-Encrypted: i=1; AJvYcCWjaFJP52DLJIp7y34+LcaIUl82YeiynlmjrdDMljWtnagRZ6df33HMtf1BTmSGSyoPaYJdq1RdmrKUa0QRqOk= X-Gm-Message-State: AOJu0YwnYbAiMiL4IdtRZX3hSwcWM11sGbINQBn5A1wi3zJ+9pSyoCKb VXXRE/84u8qmxk7JReytIn11ugcFulwUUGVOW3XRmXQjHmhjjTle4Wx1x/XeNP70SN53jwSuLIA +oc+Vplr0kzz24X+XT158G0TQmcM= X-Google-Smtp-Source: AGHT+IESFwmTu9SI2DtoE+RabymcYZln1var7ZFrcfwujTzWXEQorBN1tq8bwpLS1FGSuxRI+ELluAIzXUC/h4vmpxQ= X-Received: by 2002:a17:906:7b84:b0:a6f:12:8c45 with SMTP id a640c23a62f3a-a6f48029fd3mr108134266b.72.1718197137007; Wed, 12 Jun 2024 05:58:57 -0700 (PDT) MIME-Version: 1.0 References: <721d713f-a17b-4c77-aea8-46db06e1dd24@orange.fr> In-Reply-To: <721d713f-a17b-4c77-aea8-46db06e1dd24@orange.fr> From: Jonathan Wakely Date: Wed, 12 Jun 2024 13:58:45 +0100 Message-ID: Subject: Re: gcc git locked out for hours second day in a row To: Mikael Morin Cc: Jakub Jelinek , gcc@gcc.gnu.org, Frank Eigler Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: > > Le 12/06/2024 =C3=A0 13:48, Jakub Jelinek a =C3=A9crit : > > Hi! > > > > Yesterday the gcc git repository was locked for 3 hours > > locked by user mikael at 2024-06-11 13:27:44.301067 (pid =3D 974167) > > 78:06 python hooks/update.py refs/users/mikael/tags/fortran-dev_merges/= r10-1545 0000000000000000000000000000000000000000 c2f9fe1d8111b9671bf0aa836= 2446516fd942f1d > > 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 =3D 2219652) > > 78:06 python hooks/update.py refs/users/mikael/tags/toto 00000000000000= 00000000000000000000000000 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 comm= its. > > > > 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? > 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. > >