Gerrit 2.4.2 pushing broken?

239 views
Skip to first unread message

Markus Duft

unread,
Sep 20, 2012, 9:15:33 AM9/20/12
to repo-d...@googlegroups.com
Hi!

I just upgraded (for testing) a copy of our 2.2.2.1 instance. After upgrading everything works perfectly, /except/ that gerrit reports strange errors to the client.

If i create a single new commit and push it to refs/for and then to ref/heads it tells me change closed, and the commit is where i would expect it (so the change /is/ closed, but the close happened during the push). This really looks like [1].

However there are other things too. For example i just created a single simple commit on master, and pushed it to refs/for/master. the change appears on gerrit as expected and seems in a good shape, but the client got this:

@s01en22 /fast/wamas5/gerrit/test/wamas5 $ git push origin HEAD:refs/for/master
...
To ssh://s01en22:2501/wamas5.git
 ! [remote rejected] HEAD -> refs/for/master (diff error)
error: failed to push some refs to 'ssh://s01en22:2501/wamas5.git'

but then when i try to submit the change it tells me "Unspecified merge failure: REVISION_GONE". in the log i see:

802 [2012-09-20 15:01:48,666] ERROR com.google.gerrit.server.git.ReceiveCommits : Error computing patch of commit e5df710de6c6cdbd3845a9db44754c37aa8c1b28
803 java.io.IOException: Failed to create ref refs/changes/80/9480/1 in /fast/wamas5/gerrit/snapshot/git/wamas5.git: REJECTED
804     at com.google.gerrit.server.git.ReceiveCommits.createChange(ReceiveCommits.java:1116)
805     at com.google.gerrit.server.git.ReceiveCommits.createNewChanges(ReceiveCommits.java:1008)
806     at com.google.gerrit.server.git.ReceiveCommits.processCommands(ReceiveCommits.java:434)
807     at com.google.gerrit.server.git.AsyncReceiveCommits$Worker.run(AsyncReceiveCommits.java:90)
808     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
809     at com.google.gerrit.server.util.RequestScopePropagator$1.call(RequestScopePropagator.java:86)
810     at com.google.gerrit.server.util.ThreadLocalRequestScopePropagator$1.call(ThreadLocalRequestScopePropagator.java:58)
811     at com.google.gerrit.server.util.RequestScopePropagator$2.call(RequestScopePropagator.java:96)
812     at com.google.gerrit.server.util.RequestScopePropagator$3.run(RequestScopePropagator.java:128)
813     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
814     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
815     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
816     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
817     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
818     at com.google.gerrit.server.git.WorkQueue$Task.run(WorkQueue.java:333)
819     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
820     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
821     at java.lang.Thread.run(Thread.java:662)

then when i try to forcefully get into a working state and reset origin/master to a good state (hopefully), and i forcefully push i get:

mduft@s01en22 /fast/wamas5/gerrit/test/wamas5 $ git push origin +HEAD:refs/heads/master
Total 0 (delta 0), reused 0 (delta 0)
remote: Processing changes: refs: 2, done    
To ssh://s01en22:2501/wamas5.git
 ! [remote rejected] HEAD -> master (squash commits first)
error: failed to push some refs to 'ssh://s01en22:2501/wamas5.git'

but there is only a single commit on top of master (different to the original origin/master).

any hints?


Regards,
Markus

Markus Duft

unread,
Sep 21, 2012, 2:07:42 AM9/21/12
to repo-d...@googlegroups.com
Throwing away the whole instance and starting over put things back to (hopefully) working. i will at least create a backup of our server before migrating :D

Martin Fick

unread,
Sep 21, 2012, 2:06:06 AM9/21/12
to Markus Duft, repo-d...@googlegroups.com
I am not sure if that was really a question? We use 2.4.2+ in production, so push defs works. There is a new timeout parameter which may be bitting you, try bumping it up,

-Martin
>--
>To unsubscribe, email repo-discuss...@googlegroups.com
>More info at http://groups.google.com/group/repo-discuss?hl=en

Employee of Qualcomm Innovation Center,Inc. which is a member of Code Aurora Forum

Werner Beroux

unread,
Oct 12, 2012, 6:55:32 AM10/12/12
to repo-d...@googlegroups.com
I think this is the same issue as we're having: https://code.google.com/p/gerrit/issues/detail?id=1593
Reply all
Reply to author
Forward
0 new messages