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
Le 12/06/2024 à 14:14, Mark Wielaard a écrit :
Hi,
On Wed, 2024-06-12 at 13:48 +0200, Jakub Jelinek via Gcc wrote:
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/fortr
Le 12/06/2024 à 14:58, Jonathan Wakely a écrit :
On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc 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
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 wrote:
Le 12/06/2024 à 13:48, Jakub Jelinek a écrit :
Hi!
Yesterday the gcc git
Hello,
Le 12/06/2024 à 16:57, Jakub Jelinek a écrit :
On Wed, Jun 12, 2024 at 04:53:38PM +0200, Mikael Morin wrote:
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
