Hi Jakub, I am pushing to gfortran-test. The process seems to be finished, but is not returning (sorry it's in German):
Objekte aufzählen: 11679, fertig. Zähle Objekte: 100% (11679/11679), fertig. Delta-Kompression verwendet bis zu 28 Threads. Komprimiere Objekte: 100% (2995/2995), fertig. Schreibe Objekte: 100% (9904/9904), 10.15 MiB | 998.00 KiB/s, fertig. Gesamt 9904 (Delta 8217), Wiederverwendet 7591 (Delta 6861), Paket wiederverwendet 0 (von 0) remote: Löse Unterschiede auf: 100% (8217/8217), abgeschlossen mit 1517 lokalen Objekten. And here it hangs. I don't know what the server is doing, but my side is doing nothing. No load on CPU or network. Shall I kill the git process here? Sorry for the inconvenience. I was waiting for the server to finish whatever it is doing. - Andre On Tue, 2 Sep 2025 11:26:54 +0200 Jakub Jelinek <[email protected]> wrote: > On Tue, Sep 02, 2025 at 11:04:45AM +0200, Richard Biener via Gcc wrote: > > On Tue, Sep 2, 2025 at 11:01 AM Rainer Orth via Gcc <[email protected]> > > wrote: > > > > > > I'm currently trying to push to the repo for an hour, but only get > > > > > > remote: > > > --------------------------------------------------------------------- > > > remote: -- Another user is currently pushing changes to this repository. > > > -- remote: -- Please try again in another minute or two. > > > -- remote: > > > --------------------------------------------------------------------- > > > remote: error: hook declined to update refs/heads/master To > > > git+ssh://gcc.gnu.org/git/gcc.git ! [remote rejected] master -> > > > master (hook declined) error: failed to push some refs to > > > 'git+ssh://gcc.gnu.org/git/gcc.git' > > > > > > Another commit a few minutes before worked just fine. Is there someone > > > doing an excessive commit or has some lock been left behind? > > > > On IRC Jakub said > > > > 10:05 < jakub> locked by user vehre at 2025-09-02 07:34:09.557509 (pid = > > 3710103) > > 10:05 < jakub> 3710103 ? R 27:15 python hooks/update.py > > refs/heads/devel/gfortran-test > > cb4b73da237153871fb840a3a31a79354933a8bb > > c0159d2c27e3b9b849fee8ce8d47a92806646888 > > 10:05 < jakub> so, it isn't stale, it is actively doing something, but it > > takes more than 30 minutes already > > It is now already more than 90 minutes (and the process taking almost 14GB > of memory). > Andre, what are you trying to do, can it be killed so that others can access > the repository? If what you're trying to do needs to be really done, can it > be done in smaller steps, such that it won't lock everybody out for more > than a few minutes at a time? > > Jakub > -- Andre Vehreschild * Email: vehre ad gmx dot de
