From: Jay Soffian <jaysoffian@gmail.com>
To: "Björn Gustavsson" <bgustavsson@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push failed
Date: Sun, 24 Jan 2010 18:35:41 -0500 [thread overview]
Message-ID: <76718491001241535n7c47e898mbade26caa312b9db@mail.gmail.com> (raw)
In-Reply-To: <6672d0161001240952s7f7629a6v48f5756c083b95b5@mail.gmail.com>
2010/1/24 Björn Gustavsson <bgustavsson@gmail.com>:
> With git built from master (v1.6.6.1-436-gaba7dea),
> the following commands (run in a script):
>
> git commit --amend -m "Update index.html" index.html
> git push erlang +gh-pages
>
> failed like this:
>
> Counting objects: 4, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (2/2), done.
> Writing objects: 100% (3/3), 3.85 KiB, done.
> Total 3 (delta 0), reused 0 (delta 0)
> error: Ref refs/heads/gh-pages is at
> db10c045e068f12aa2f78377fab31e35a8443ca4 but expected
> 054136d96494979b42524a4dc08ef643bb54cc0e
> error: failed to lock refs/heads/gh-pages
> To git@erlang_github.com:erlang/otp.git
> ! [remote rejected] gh-pages -> gh-pages (failed to lock)
> error: failed to push some refs to 'git@erlang_github.com:erlang/otp.git'
>
> Unfortunately (from the point of view of finding the bug), the
> problem is not reproducible. When I ran my script two more times,
> it worked fine.
>
> We all know how difficult it is to investigate non-reproducible bugs,
> but perhaps someone familiar with the code might have some idea
> about what it could be.
>
> Info about my system:
>
> Mac OS X 10.2.6 (8 cores)
> gcc-4.2.1
As another data point, I've noticed the same issue pushing from one
Mac OS X 10.6.2 system to another. However, the remote end is updated
properly (if you push again you'll see there's nothing to update), so
I've not bothered to dig into what the cause might be.
j.
prev parent reply other threads:[~2010-01-24 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 17:52 git push failed Björn Gustavsson
2010-01-24 23:35 ` Jay Soffian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76718491001241535n7c47e898mbade26caa312b9db@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=bgustavsson@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).