That's this patch, which isn't +2ed yet: https://gerrit.cloudera.org/#/c/4655/
I checked, and that's the only patch in refs/for/master that's not in master, though master has a few changes not in refs/for/master: +commit 61fcb489745f3f0b3f1abbf9fbf666a29a6363de +commit 0fbb5b7e71e55346c8b97ec143854dba0088f124 +commit ff6b450ad380ce840e18875a89d9cf98058277a3 +commit 51268c053ffe41dc1aa9f1b250878113d4225258 +commit 48085274fa8ae57453477db21dae0e53eae6b766 +commit e39f1676e1c9269fb6549e8c319adf1a7ea9d445 +commit d1d88aaccd03c461c4ce6224f765afe94b7c073b +commit 8d7b01faea6362af675a2a335b462fad3e0caa03 +commit 8a49ceaae532163f17836b1050b639329424ee5c +commit 041fa6d946e1cbe309593c4a5515bef88e06cdb4 +commit f8d48b8582b9e460c2e0e3dbb4881636f179ae73 +commit 9ef9512e5b58a75e075538b3b94ac551363609e5 +commit 2fa1633e4090000e9018c012df81f291a0d7566e On Mon, Oct 24, 2016 at 2:06 PM, Jim Apple <[email protected]> wrote: > Doing a git fetch of the gerrit server, I see > > * [new branch] refs/for/master -> gerrit-asf/refs/for/master > > I'm not sure what's going on with that - the "master" branch is pushed > to by "refs/for/master" or "refs/drafts/master", so this could be a > typo of some sort. > > The commit 119bff3ac17f847f1a4137ea56707c72cd1119be is on > refs/for/master without a "Reviewed-on" line. Tim, could you take a > look? It's > > IMPALA-1430,IMPALA-4108: codegen all builtin aggregate functions > > On Mon, Oct 24, 2016 at 1:57 PM, Jim Apple <[email protected]> wrote: >> What do you think we should force-push? >> >> What did we do to cause it, and how can we avoid it in the future? >> >> On Mon, Oct 24, 2016 at 12:40 PM, Henry Robinson <[email protected]> wrote: >>> I also saw the same thing. The way I got around it was to try pushing to >>> /drafts/ and then publishing it, which worked. >>> >>> We might need to force-push to gerrit/master to clean this up. >>> >>> On 24 October 2016 at 12:37, Lars Volker <[email protected]> wrote: >>> >>>> I tried to push another patch set to Gerrit and got the error below. This >>>> worked about an hour ago and now stopped working. The local parent commit >>>> is the same one as remote, I didn't rebase either. Has anyone seen this >>>> before? I suspect I can rebase but then the review gets much more tedious >>>> to follow. >>>> >>>> Thanks, Lars >>>> >>>> ✔ ~/i2(i2521) ✗$ git push asf HEAD:refs/for/master >>>> To ssh://gerrit.cloudera.org:29418/Impala-ASF >>>> ! [rejected] HEAD -> refs/for/master (non-fast-forward) >>>> error: failed to push some refs to 'ssh:// >>>> [email protected]:29418/Impala-ASF' >>>> hint: Updates were rejected because a pushed branch tip is behind its >>>> remote >>>> hint: counterpart. Check out this branch and integrate the remote changes >>>> hint: (e.g. 'git pull ...') before pushing again. >>>> hint: See the 'Note about fast-forwards' in 'git push --help' for details. >>>> ✗ ~/i2(i2521) ✗$ >>>> >>> >>> >>> >>> -- >>> Henry Robinson >>> Software Engineer >>> Cloudera >>> 415-994-6679
