GCC repo is locked?

← All discussions

Project / Subsystem

gcc / gcc

Date

2026-07-24

Proposer

"H.J. Lu" <hjl.tools@gmail.com>

Source type

public_inbox

Consensus

Proposed

Sentiment

8/10

Technical tradeoffs

  • • The locking mechanism prevents race conditions during pushes but can cause temporary unavailability if a process hangs or is misunderstood.
  • • Manual intervention is required to resolve hook-related deadlocks, highlighting a potential need for more robust automated recovery or clearer protocols.

All attributes

project
gcc
subsystem
gcc
patch_id
—
discussion_id
CAMe9rOrW5KaH5Od1dz=v1kuknOONHRQjQWYXRsznsaCUu6saMA@mail.gmail.com
source_type
public_inbox
title
GCC repo is locked?
headline
GCC repo is locked?
tldr
Pushing to GCC repository blocked by hook, but resolved after process termination.
proposer
"H.J. Lu" <hjl.tools@gmail.com>
consensus
Proposed
outcome
proposed
sentiment_score
8
technical_tradeoffs
  • • The locking mechanism prevents race conditions during pushes but can cause temporary unavailability if a process hangs or is misunderstood.
  • • Manual intervention is required to resolve hook-related deadlocks, highlighting a potential need for more robust automated recovery or clearer protocols.
series_id
—
series_role
standalone
series_parts
[]
tags
  • • git
  • • repository
  • • push
  • • hook
  • • lock
bugzilla_url
—
date
2026-07-24T00:00:00.000Z

GCC repo is locked?

A developer reported being unable to push to the GCC repository for 15 minutes due to a “Another user is currently pushing” error, indicating a hook declined the update. Another participant confirmed they were the cause, having attempted to kill a push hook process, and subsequently terminated the process and removed the lock file, resolving the issue.