00:06:13  * jenkins-monitorquit (Remote host closed the connection)
00:06:24  * jenkins-monitorjoined
00:20:59  * williamkapkejoined
00:34:27  * Fishrock123quit (Remote host closed the connection)
00:35:08  * Fishrock123joined
00:35:15  * Fishrock123quit (Remote host closed the connection)
02:03:37  * Fishrock123joined
02:07:40  * Fishrock123quit (Ping timeout: 240 seconds)
03:11:46  * TimothyGuquit (*.net *.split)
03:19:56  * TimothyGujoined
03:27:21  * Fishrock123joined
03:28:35  * Fishrock123quit (Remote host closed the connection)
06:07:44  * Fishrock123joined
06:07:52  * Fishrock123quit (Remote host closed the connection)
09:25:18  * mattloringquit
09:25:31  * mattloringjoined
09:36:01  * node-ghjoined
09:36:01  * node-ghpart
09:39:26  * node-ghjoined
09:39:26  * node-ghpart
09:40:54  * node-ghjoined
09:40:54  * node-ghpart
09:48:26  * node-ghjoined
09:48:26  * node-ghpart
09:58:13  * bzozquit
09:58:28  * bzozjoined
10:12:33  * Trottquit
10:12:47  * Trottjoined
10:25:10  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
11:32:45  * D4R5C0D3joined
12:07:14  * Fishrock123joined
12:07:31  * gibfahnjoined
12:08:19  <gibfahn>jbergstroem: you around? Not sure what time of the morning it is for you.
12:08:36  <jbergstroem>not early enough to blame i was afk :P
12:11:02  <gibfahn>Haha, perfect
12:11:27  * Fishrock123quit (Ping timeout: 240 seconds)
12:11:32  <gibfahn>So we're looking at having a job to update the canary branch and run CI on it, see https://github.com/nodejs/build/issues/626#issuecomment-299138650
12:11:42  <gibfahn>Job is: https://ci.nodejs.org/view/All/job/node-update-v8-canary/
12:11:57  <gibfahn>The question is what to do about committing and pushing.
12:12:21  * targosjoined
12:12:36  <gibfahn>What should the commit username and email be, and should we push to nodejs/node or nodejs/something-else?
12:15:43  <gibfahn>jbergstroem: and actually if you said it was still 6:30 there I'd believe you :)
12:17:19  <jbergstroem>hm
12:19:01  <gibfahn>Currently Michael (@targos) force-pushes to nodejs/node:canary every time he updates.
12:29:53  <gibfahn>Michael (@mhdawson) suggested that we create nodejs/node-v8 and push to that, that way we can not allow the user to push to nodejs/node itself, which should be safer.
12:30:12  <gibfahn>Not sure what the process is for adding new repos to nodejs
12:32:19  <jbergstroem>yeah i think that should be the way
12:32:31  <gibfahn>jbergstroem: if we did that then maybe we could add a deploy key to nodejs/node-v8, and as long as that key doesn't have access to nodejs/node then it's reasonably safe.
12:32:37  <gibfahn>Is there an ssh key we should use?
12:32:49  <gibfahn>Can we just add a repo? Not sure if there's a process.
12:33:03  <jbergstroem>we should move joaocgreis repo for binary stuff into our org too
12:33:20  <jbergstroem>i don't know to be hoenst (aobut adding repos). usually no probs
12:33:31  <jbergstroem>perhaps put a "build" in there
12:33:35  <jbergstroem>if its for build purposes only
12:33:56  <gibfahn>Ideally it would be the master branch but with the latest V8, so not just for build
12:34:10  <gibfahn>Like node-chakracore but for V8, so people can try the latest V8.
12:34:32  <gibfahn>Followup question is whether we can trigger nightly builds and have them go to nodejs.org
12:38:22  <joaocgreis>gibfahn: take a look at the end of the compile jobs, node-compile-windows and node-cross-compile, they commit and push to the temp repo
12:39:40  <joaocgreis>keys are in secrets, the github used was created by me for exactly that purpose (email is an alias in email repo)
12:39:57  <gibfahn>Perfect, thanks joao.
12:40:14  <gibfahn>So that key doesn't have push access to nodejs/node right?
12:41:40  <joaocgreis>gibfahn: no, and we should be careful with that. Giving jenkins push access is tricky
12:41:50  <gibfahn>Yeah that's what I was hoping you'd say
12:41:59  <gibfahn>I want to make sure the job doesn't push to nodejs/node by mistake.
12:42:22  * Michele_joined
12:42:26  <gibfahn>joaocgreis: so are you okay with us giving that key push access to nodejs/node-v8 (which we're creating)?
12:43:07  <joaocgreis>gibfahn: okay by me
12:46:08  <Michele_>jbergstroem i would like to start testing your refactor-the-world pr. My idea was to run scripts against a linux virtual machine on my mac as first round, so basically cleaning up inventory and just leave my vm. Do you think is good way for testing it, since i don't have access to cloud machines?
12:53:16  * D4R5C0D3quit (Read error: Connection reset by peer)
12:53:18  <jbergstroem>Michele_: yes that's what i do. a lot of testing against vm. you can actually pretty easily hook docker instances up too; but they will fail on things like reboot
12:54:25  <gibfahn>joaocgreis: I can't see the public key for that secret, not sure if I'm doing it wrong, `dotgpg cat infra/ci-iojs-org-id_rsa-github.pub` doesn't work for me.
12:54:49  <Michele_>jbergstroem: ok i'll use VM with parallels. Is there any particular os that you want me to test first? Othrwise i'll start with a ubuntu server
12:55:17  <jbergstroem>Michele_: up to you :) feel free to nag me in private as you go
12:55:54  <Michele_>jbergstroem: ok, thanks. I'll start with Ubuntu 16.04
13:00:23  <gibfahn>joaocgreis: `ci-iojs-org-id_rsa-github.pub: Decryption failed`, I think maybe I don't have access
13:00:45  <gibfahn>As it's the public key, any chance you can just send it to me?
13:03:24  <joaocgreis>gibfahn: sure. The private is already in jenkins. Let me send it
13:04:21  <gibfahn>Thanks. gibfahn@gmail.com is fine
13:07:39  <joaocgreis>gibfahn: sent!
13:08:10  <gibfahn>Thanks
13:11:56  <gibfahn>https://help.github.com/articles/error-key-already-in-use/
13:12:12  <gibfahn>Getting this error, apparently you can't have one key authed to more than one account or user.
13:12:20  <gibfahn>So I guess we need another key
13:17:12  <gibfahn>joaocgreis: what's the easiest way to add a key to the secrets repo so it's available in Jenkins?
13:17:30  <gibfahn>Am I okay to just add one?
13:18:22  <joaocgreis>gibfahn: are you adding a new github user?
13:18:42  <gibfahn>Was going to just add a deploy key
13:18:55  <gibfahn>to the newly created nodejs/node-v8 repo
13:19:19  <joaocgreis>you can add nodejs-ci as a collaborator with write access
13:19:37  <joaocgreis>that's how it's currently done for the temp repo
13:19:49  <gibfahn>Oh okay, that should work
13:20:33  <gibfahn>Invite sent, could you accept?
13:22:16  <joaocgreis>gibfahn: done
13:25:24  * D4R5C0D3joined
13:45:15  <gibfahn>jbergstroem: (or joaocgreis ) targos suggested that we skip the node-test-commit tests for arm, as it takes several hours to build with the updated V8. Is there a NODES_SUBSET that does that?
13:45:59  <jbergstroem>i haven't done much of that; joaocgreis probs knows better
13:46:35  <joaocgreis>gibfahn: no..
13:47:02  <joaocgreis>don't think that'd be easy to create without braking anything
13:47:09  <gibfahn>What does NODES_SUBSET=="0.12" set?
13:47:32  * chorrelljoined
13:47:33  <gibfahn>Does that skip arm?
13:47:51  <joaocgreis>v0.x skips arm but also some others, is that ok?
13:48:20  <joaocgreis>note windows tests don't divide by 4, will take longer but run them all
13:49:40  <joaocgreis>I believe it skips newer versions of smartos, aix, linuxone, etc. (new platforms that are not supported by v0.x)
13:51:14  <joaocgreis>you might consider duplicating node-test-commit, then you can control exactly what platforms it runs
13:51:36  <gibfahn>Yeah that's probably a good idea
14:15:24  * evanlucasquit (Remote host closed the connection)
14:16:58  * node-ghjoined
14:16:58  * node-ghpart
14:19:09  * node-ghjoined
14:19:09  * node-ghpart
14:20:12  * rmg_joined
14:21:49  * node-ghjoined
14:21:49  * node-ghpart
14:22:10  * Michele_quit (Ping timeout: 260 seconds)
14:22:45  * node-ghjoined
14:22:46  * node-ghpart
14:23:35  <gibfahn>Okay great, so we have the update and the test job, they seem to be running alright.
14:23:41  <gibfahn>Next question is nightly builds
14:23:41  * rmgquit (Ping timeout: 255 seconds)
14:24:01  <gibfahn>Is this something we need to discuss in build, or can we just add a trigger to the release job?
14:24:12  <gibfahn>Followup question, how do you add it to the release job?
14:24:22  <gibfahn>Details here: https://github.com/nodejs/build/issues/626#issuecomment-299138650
14:27:19  * node-ghjoined
14:27:19  * node-ghpart
14:31:16  * node-ghjoined
14:31:17  * node-ghpart
14:31:31  * D4R5C0D3quit (Read error: Connection reset by peer)
14:32:32  * D4R5C0D3joined
14:33:52  * D4R5C0D3quit (Remote host closed the connection)
14:52:10  * targosquit (Ping timeout: 240 seconds)
14:57:10  * gibfahnquit (Ping timeout: 260 seconds)
15:11:40  * evanlucasjoined
15:20:34  * evanlucasquit (Remote host closed the connection)
15:22:43  * ofrobotsjoined
15:23:36  * Fishrock123joined
16:35:40  * mattloringquit (Remote host closed the connection)
16:35:40  * bzozquit (Remote host closed the connection)
16:35:40  * Trottquit (Remote host closed the connection)
16:44:17  * Trottjoined
16:44:39  * bzozjoined
16:46:22  * mattloringjoined
17:12:31  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:24:30  * Fishrock123quit (Remote host closed the connection)
17:52:01  * chorrelljoined
17:57:27  * Fishrock123joined
18:35:02  * jenkins-monitorquit (Remote host closed the connection)
18:35:10  * jenkins-monitorjoined
18:38:28  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:40:02  * jenkins-monitorquit (Remote host closed the connection)
18:40:12  * jenkins-monitorjoined
18:42:19  * chorrelljoined
18:45:02  * jenkins-monitorquit (Remote host closed the connection)
18:45:10  * jenkins-monitorjoined
18:46:57  * kfarnungjoined
18:49:47  <kfarnung>I'm seeing a "502 Bad Gateway" response when trying to connect to https://ci.nodejs.org/, can anyone else connect successfully?
18:50:02  * jenkins-monitorquit (Remote host closed the connection)
18:50:09  * jenkins-monitorjoined
18:55:02  * jenkins-monitorquit (Remote host closed the connection)
18:55:09  * jenkins-monitorjoined
19:00:02  * jenkins-monitorquit (Remote host closed the connection)
19:00:09  * jenkins-monitorjoined
19:05:01  * jenkins-monitorquit (Remote host closed the connection)
19:05:10  * jenkins-monitorjoined
19:10:02  * jenkins-monitorquit (Remote host closed the connection)
19:10:11  * jenkins-monitorjoined
19:15:02  * jenkins-monitorquit (Remote host closed the connection)
19:15:37  * jenkins-monitorjoined
19:20:02  * jenkins-monitorquit (Remote host closed the connection)
19:20:10  * jenkins-monitorjoined
19:25:02  * jenkins-monitorquit (Remote host closed the connection)
19:25:10  * jenkins-monitorjoined
19:28:15  * mscdexjoined
19:28:28  <mscdex>ci is giving 502 bad gateway immediately when trying to navigate to any jenkins page
19:30:01  * jenkins-monitorquit (Remote host closed the connection)
19:30:13  * jenkins-monitorjoined
19:35:02  * jenkins-monitorquit (Remote host closed the connection)
19:35:10  * jenkins-monitorjoined
19:40:01  * jenkins-monitorquit (Remote host closed the connection)
19:40:09  * jenkins-monitorjoined
19:45:02  * jenkins-monitorquit (Remote host closed the connection)
19:45:09  * jenkins-monitorjoined
19:50:02  * jenkins-monitorquit (Remote host closed the connection)
19:50:09  * jenkins-monitorjoined
19:51:28  <Trott>jbergstroem: ^^^^^
19:51:38  <jbergstroem>checking
19:52:10  <jbergstroem>[12620358.849972] Killed process 3557 (java) total-vm:36588468kB, anon-rss:28882056kB, file-rss:0kB
19:52:18  <jbergstroem>Trott: thanks for the ping (i get phone notifications)
19:53:01  <jbergstroem>kfarnung, mscdex: coming back now
19:53:28  <jbergstroem>going to check if we can switch to a systemd unit to auto-restart on crash
19:59:55  <mscdex>seems to be back up and working now, thanks jbergstroem!
20:00:08  <jbergstroem>mscdex: yeah; oom'ed (above)
20:00:26  <mscdex>yep
20:56:52  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:02:29  * Fishrock123quit (Remote host closed the connection)
21:05:12  * chorrelljoined
21:06:04  * Fishrock123joined
21:10:25  * node-ghjoined
21:10:25  * node-ghpart
21:14:55  * node-ghjoined
21:14:55  * node-ghpart
21:15:08  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:15:30  * node-ghjoined
21:15:30  * node-ghpart
21:15:32  * chorrelljoined
21:15:56  * chorrellquit (Client Quit)
21:16:26  * lanceballchanged nick to lance|afk
21:16:35  * chorrelljoined
21:16:44  * chorrellquit (Client Quit)
21:17:12  * chorrelljoined
21:17:32  * chorrellquit (Client Quit)
21:18:02  * chorrelljoined
21:18:20  * chorrellquit (Client Quit)
21:18:51  * chorrelljoined
21:19:08  * chorrellquit (Client Quit)
21:19:14  * lance|afkchanged nick to lanceball
21:19:16  * lanceballchanged nick to lance|afk
21:28:29  <kfarnung>jbergstroem: Thanks!
21:28:42  <jbergstroem>kfarnung: thanks for reporting
21:28:45  * Fishrock123quit (Remote host closed the connection)
21:29:36  * Fishrock123joined
21:48:41  * kunalspathakjoined
22:02:53  * node-ghjoined
22:02:53  * node-ghpart
22:56:47  * node-ghjoined
22:56:47  * node-ghpart
23:02:59  * Fishrock123quit (Quit: Leaving...)
23:31:16  * chorrelljoined
23:36:13  * chorrellquit (Ping timeout: 268 seconds)