BTW: as a stopgap presumably presumably one of us can just sync down the upstream and push it to the upstream mirror?  We don't need to do a force push here (since it doesn't involve a rebase) so I believe we have access.

You probably don't have permission to push -- the repos which are automatically mirrored disallow pushes from everyone except for the mirror process.

Unassigning from myself, as this should be handled by the current Git Admin. (Please don't directly assign Infra-Git bugs; we have a triage rotation for that.)

*ping*

Has anybody had a chance to look into this yet? It's blocking development for us because we can't sync our master to the newest patches that landed upstream. Is there any other component or label I need to add to this bug to make sure it gets picked up?

(Marking P-0... we don't exactly need it today, but some time within the next few days to make sure we can continue working uninterrupted.)

Looking into this. I don't know why the previous git admin ignored this.

I don't see evidence of a force push... last commit on the mirror is c29164179588f066c7d07868a5ae3ce7dbc88fca, which occurs on refs/heads/master in github.

Uhm... the copy config is present, but disabled:

    remote_config: <
      owner: <
        LdapUser: "agable"
      >
      url: "https://github.com/ARM-software/arm-trusted-firmware.git"
      fetch: "+refs/heads/*:refs/heads/upstream_mirror/*"
      fetch: "+refs/tags/*:refs/tags/*"
      fetch_remove_deleted: false
      fetch_poll_frequency_sec: 600
      disabled: true
    >

Does that sound familiar to anyone? Otherwise I'll just un-disable it.

Talking to gob oncall, it may have self-disabled because of too many fetch errors. I'm re-enabling it now.

Looks happy again

Thanks for the quick action!

Can you please follow up on this self-disabling and try to find a way to prevent that from happening again? It's important for us that this sync happens without silent interruptions. If this is some kind of important safeguard that cannot be removed, it should at least send and email or open a bug somewhere to notify us of the problem.

Bulk verified

bulk verified