Repository navigation
attempt-backport still does not work Edit: now working?! #100
Copy link
Copy link
Closed
Description
@rvagg had updated the git version to see if that was the issue was just an old git version.
I added an extra cleanup step and tested things thoroughly locally... All still worked.
nodejs/node#10181 is an example of it failing.
It lands cleanly all the way to v4, but the bot thought it was dont-land-on-v7.x.
Here's some bot output:
relevant bot logs
12:05:27.711 DEBUG bot: processing a new backport to v7 (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:27.711 DEBUG bot: aborting any previous backport attempt... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:27.716 INFO bot: request finish (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, duration=7, req.query={}, req.remoteAddress=::ffff:192.30.252.42, req.remotePort=61138)
POST /hooks/github HTTP/1.1
host: github-bot.nodejs.org:3333
accept: */*
user-agent: GitHub-Hookshot/4f5b94b
x-github-event: pull_request
x-github-delivery: 83fca580-bd68-11e6-9f8a-82fea636fda2
content-type: application/json
x-hub-signature: null
content-length: 19641
--
HTTP/1.1 200 OK
HTTP/1.1 200 OK
X-Powered-By: Express
X-Request-Id: ac0bc597-a8ed-410f-a253-8cfdbabd7324
Date: Thu, 08 Dec 2016 17:05:27 GMT
Connection: keep-alive
Content-Length: 0
12:05:27.723 DEBUG bot: resetting origin/v7.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:29.565 DEBUG bot: updating git remotes... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:29.717 DEBUG bot: Fetching PR files for labelling (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:30.228 DEBUG bot: Filled existing repo labels cache: addons,aix,arm,assert,async_hooks,async_wrap,benchmark,blocked,buffer,build,c++,cares,child_process,cluster,code-and-learn,confirmed-bug,console,crypto,ctc-agenda,ctc-review,debugger,dgram,discuss,dns,doc,domain,dont-land-on-v4.x,dont-land-on-v6.x,dont-land-on-v7.x,duplicate,errors,events,feature request,freebsd,fs,good first contribution,help wanted,http,https,http_parser,in progress,install,intl,invalid,land-on-v4.x,land-on-v6.x,lib / src,libuv,lts,lts-agenda,lts-watch-v0.12,lts-watch-v4.x,lts-watch-v6.x,macos,memory,mentor-available,meta,mips,module,net,notable-change,npm,openssl,os,path,performance,post-mortem,ppc,process,promises,punycode,querystring,question,readline,repl,repro-exists,s390,security,semver-major,semver-minor,smartos,stalled,stream,string_decoder,test,timers,tls,tools,tty,url,util,v0.12,v4.x,v6.x,v7.x,V8,V8_inspector,vm,windows,wontfix,zlib (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:30.229 DEBUG bot: Resolved labels: test (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:30.229 DEBUG bot: Trying to add labels: test (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:30.419 INFO bot: Added labels: test (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:30.739 INFO bot: Emitting GitHub event (req_id=221df042-0235-488f-8560-df45d39d48f0, pr=nodejs/node/#10181, action=pull_request.labeled)
12:05:30.740 INFO bot: request finish (req_id=221df042-0235-488f-8560-df45d39d48f0, duration=2, req.query={}, req.remoteAddress=::ffff:192.30.252.40, req.remotePort=49977)
POST /hooks/github HTTP/1.1
host: github-bot.nodejs.org:3333
accept: */*
user-agent: GitHub-Hookshot/4f5b94b
x-github-event: pull_request
x-github-delivery: 85c66900-bd68-11e6-8e52-c3e7d940b701
content-type: application/json
x-hub-signature: null
content-length: 19945
--
HTTP/1.1 200 OK
HTTP/1.1 200 OK
X-Powered-By: Express
X-Request-Id: 221df042-0235-488f-8560-df45d39d48f0
Date: Thu, 08 Dec 2016 17:05:30 GMT
Connection: keep-alive
Content-Length: 0
12:05:32.159 DEBUG bot: checking out origin/v7.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.557 DEBUG bot: resetting origin/v7.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.749 DEBUG bot: fetching diff from pr 10181... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.750 DEBUG bot: attempting a backport to v7... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.757 DEBUG bot: backport to 7 failed (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.757 DEBUG bot: Trying to add labels: dont-land-on-v7.x (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.764 DEBUG bot: processing a new backport to v6 (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.764 DEBUG bot: aborting any previous backport attempt... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.768 DEBUG bot: resetting origin/v6.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:32.943 INFO bot: Added labels: dont-land-on-v7.x (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:33.113 INFO bot: Emitting GitHub event (req_id=5d263e80-f80f-4c98-b302-d8896415b5f0, pr=nodejs/node/#10181, action=pull_request.labeled)
12:05:33.115 INFO bot: request finish (req_id=5d263e80-f80f-4c98-b302-d8896415b5f0, duration=2, req.query={}, req.remoteAddress=::ffff:192.30.252.40, req.remotePort=60736)
POST /hooks/github HTTP/1.1
host: github-bot.nodejs.org:3333
accept: */*
user-agent: GitHub-Hookshot/4f5b94b
x-github-event: pull_request
x-github-delivery: 86f79600-bd68-11e6-80cc-443116482953
content-type: application/json
x-hub-signature: null
content-length: 19971
--
HTTP/1.1 200 OK
HTTP/1.1 200 OK
X-Powered-By: Express
X-Request-Id: 5d263e80-f80f-4c98-b302-d8896415b5f0
Date: Thu, 08 Dec 2016 17:05:33 GMT
Connection: keep-alive
Content-Length: 0
12:05:33.684 DEBUG bot: updating git remotes... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.178 DEBUG bot: checking out origin/v6.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.599 DEBUG bot: resetting origin/v6.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.731 DEBUG bot: fetching diff from pr 10181... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.732 DEBUG bot: attempting a backport to v6... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.740 DEBUG bot: backport to 6 failed (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.740 DEBUG bot: processing a new backport to v4 (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.740 DEBUG bot: aborting any previous backport attempt... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:34.743 DEBUG bot: resetting origin/v4.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:35.751 DEBUG bot: updating git remotes... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:36.239 DEBUG bot: checking out origin/v4.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:36.630 DEBUG bot: resetting origin/v4.x-staging... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:36.768 DEBUG bot: fetching diff from pr 10181... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:36.770 DEBUG bot: attempting a backport to v4... (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
12:05:36.780 DEBUG bot: backport to 4 failed (req_id=ac0bc597-a8ed-410f-a253-8cfdbabd7324, pr=nodejs/node/#10181, action=pull_request.opened)
... deploying some extra debugging live now ...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
attempt-backport: enable/add debug info for prod
attempt-backport: enable/add debug info for prod
Fishrock123 commentedon Dec 8, 2016
also nodejs/node#10182
Fishrock123 commentedon Dec 8, 2016
x_x
It turns out it was failing because there was no git author set.
The full output if anyone is that curious...
Fishrock123 commentedon Dec 8, 2016
another: nodejs/node#10183
attempt-backport: enable/add debug info for prod
[-]attempt-backport still does not work[/-][+]attempt-backport still does not work Edit: working?[/+]Fishrock123 commentedon Dec 8, 2016
Ok. I think I got the git author/user set now... although probably not properly, but it works.
Here's the logs from nodejs/node#9773, which appears to have been successful run and verified correct locally. (No labels should have been set.)
Log snippit
MylesBorins commentedon Dec 8, 2016
Fishrock123 commentedon Dec 8, 2016
I already cleaned them up. They would only ever have been the
dont-land-on-v7.xsince the lts labels only apply if it passes.targos commentedon Dec 9, 2016
The bot keeps adding labels that are already present and it can be a bit noisy if there are many pushes: nodejs/node#9283
Can we do something about it?
MylesBorins commentedon Dec 9, 2016
Perhaps we can do a diff against current labels and only update if there is a change. The check is good, as it may be possible between pushes for something to no longer land cleanly, and that would be a good thing to find out
phillipj commentedon Dec 10, 2016
Sounds good. Such a change would probably be in lib/node-repo.js#updatePrWithLabels() if anyone wants to give it a shot.
Fishrock123 commentedon Dec 11, 2016
I started on this yesterday but haven't gotten to it yet this weekend. It has some nuance in that it would probably be best to also have it check if it previously labeled what would now be incorrect and removed previous labels it applied. Again, started on it but...
[-]attempt-backport still does not work Edit: working?[/-][+]attempt-backport still does not work Edit: now working?![/+]5 remaining items
Fishrock123 commentedon Dec 13, 2016
Here's a different one...
nodejs/node#10159 4 days ago (during the timeframe?) labeled as backport to v4 even though inspector doesn't even exist on v4.
Fishrock123 commentedon Dec 13, 2016
UH OH.
Problem is occurring again. This time I have logs on and this is showing up:
Digging though the logs more to try to find what started it.
Fishrock123 commentedon Dec 13, 2016
Ok I think it started here:
Looks like there is a bug where parallel access to the git repo can occur. :/
Thought I guarded well against that but I guess not well enough.
Fishrock123 commentedon Dec 13, 2016
Of note:
Perhaps there is a bug where that queuing logic does not work correctly if a second request comes in at certain stages during an existing request.
phillipj commentedon Dec 14, 2016
Also worth mentioning for others not knowing the deployment details; there's only one bot process running.
joaocgreis commentedon Dec 15, 2016
Here is another one: nodejs/node#10156 . 20h ago was the last time it added the
dont-land-on-v7.xlabel, then 19h ago it added only thelts-watchlabels.Fishrock123 commentedon Dec 15, 2016
Ok. I've also realized that this step is incorrect. It should be resetting to whatever the branch was, not the branch we want to switch to.
The options are:
git amstate which we already cleanly get rid of each time.Fishrock123 commentedon Dec 15, 2016
But I don't think the above should fail in that way or cause this? The logs do point to it though...? :/
attempt-backport: simplify git steps
Fishrock123 commentedon Dec 15, 2016
#107 might fix the overarching issue. (maybe. (?))
It does remove the (almost certainly) unnecessary step(s) I just described though.
attempt-backport: simplify git steps
Fishrock123 commentedon Jan 4, 2017
I think #107 fixed it since no-one has yelled my way in the past 3 weeks lol
phillipj commentedon Jan 10, 2017
Might look like there's still something fishy.
I just rebased nodejs/node#6601 against master and it got labeled with
dont-land-on-v7.xwith the following visible in the logs:That patch lands cleanly on master for me :/
phillipj commentedon Jan 10, 2017
^ doh nevermind. Forgot master !== v7. I get the same issues as seen in the logs when trying to land patch on
v7.x-staging.