Last modified: 2014-11-16 07:32:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42946, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40946 - Unable to resubmit an existing patchset
Unable to resubmit an existing patchset
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-11 12:24 UTC by Liangent
Modified: 2014-11-16 07:32 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Liangent 2012-10-11 12:24:55 UTC
I submitted a patchset to gerrit but forgot to type branch name and it's sent to master and some new changesets are created. After I realized my error I abandoned them from web then use the correct command to send it to my branch but it's rejected by gerrit, with the following message: 

To ssh://liangent@gerrit.wikimedia.org:29418/mediawiki/core.git
 ! [remote rejected] HEAD -> refs/publish/chinese-collation/chinese-collation (no new changes)
error: failed to push some refs to 'ssh://liangent@gerrit.wikimedia.org:29418/mediawiki/core.git'
Comment 1 Liangent 2012-10-11 12:27:28 UTC
To resolve that I rebased my branch against master to force a hash change then successfully submitted it...
Comment 2 Chad H. 2012-10-11 12:29:08 UTC
WORKSFORME then?
Comment 3 Liangent 2012-10-11 12:33:07 UTC
(In reply to comment #2)
> WORKSFORME then?

How did you test it?
Comment 4 Chad H. 2012-10-11 12:36:30 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > WORKSFORME then?
> 
> How did you test it?

I didn't, but you said you managed to find a workaround. I'm not really sure what needs to be done here.
Comment 5 Chad H. 2012-10-11 12:38:51 UTC
Actually, you might be hitting this upstream bug:

https://code.google.com/p/gerrit/issues/detail?id=648
Comment 6 Liangent 2012-10-11 12:41:12 UTC
(In reply to comment #5)
> Actually, you might be hitting this upstream bug:
> 
> https://code.google.com/p/gerrit/issues/detail?id=648

Yep, or better to say http://code.google.com/p/gerrit/issues/detail?id=1153

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links