00:24:55  * node-ghjoined
00:24:55  * node-ghpart
01:07:24  * bambams21joined
01:10:28  * bambams21quit (Remote host closed the connection)
01:27:31  * blocked19joined
01:30:52  * blocked19quit (Remote host closed the connection)
01:51:15  * richardlaujoined
02:21:59  <richardlau>This is just an observation but it's been very confusing today seeing what looks like CI's being started in PR's while the lockdown is in effect.
02:23:05  <refack>I get what you are saying...
02:23:29  <richardlau>and I mean in PR's that are not related to the releases being prepped
02:23:55  <Trott>co-sign
02:24:20  <Trott>I mean, I'm not sure there's anything simple to do about it. Just observing.
02:24:52  <refack>Write up a clarification...
02:26:39  <Trott>Yeah, document it and get the word out to the peoples. That's about it, I think.
02:38:33  <maclover7>Add a mention in the docs where we talk about how to announce the CI lockdown would be good
02:38:34  <maclover7>https://github.com/nodejs/build/blob/master/doc/jenkins-guide.md#before-the-release
02:39:05  <maclover7>rvagg: can you confirm things are good for me to open back up the public CI?
02:39:15  <rvagg>jenkins upgrade still required, will do that when I'm done with the releases and let you know
02:39:57  <maclover7>ok, no worries
02:42:15  <richardlau>From the linked docs I don't think this happened: "Make a post in the nodejs/collaborators discussion page to let users of the public CI know that their access will be curtailed. Be sure to insert a link to the nodejs/build tracking issue."
02:42:41  * node-ghjoined
02:42:42  * node-ghpart
02:45:45  <rvagg>https://github.com/nodejs/build/issues/1442 richardlau
02:46:08  <rvagg>"nodejs/collaborators discussion page" - what is this thing?
02:46:41  <refack>It's a GitHub bug - https://github.com/orgs/nodejs/teams/collaborators
02:46:48  <refack>(a.k.a. broken feature)
02:47:07  <refack>The CommComm want to deprecate it's use.
02:47:29  <rvagg>ah, yeah, visibility on those things is garbage
02:47:29  <refack>private is not private. and public is not public
02:49:02  <rvagg>refack, maclover7: do you want me to wait for your CI jobs or shal I kill them?
02:49:16  <refack>mine you can kill
02:49:44  <maclover7>Mine's just a run on master to make sure things are okay, nothing secret in there
02:50:43  <maclover7>richardlau: Yeah I ended up making a build issue (I find that easier personally)
02:50:48  <maclover7>.All that's (probably) needed is just a nudge to not use CI for non-security-release things
02:51:30  <maclover7>(ah, if you're holding on the jenkins upgrade for my job to complete, you can cancel it)
02:52:45  * node-ghjoined
02:52:45  * node-ghpart
02:53:14  * node-ghjoined
02:53:15  * node-ghpart
02:55:48  <rvagg>ugh, ci-release jenkins is borked after upgrade
02:55:50  <rvagg>won't start
02:56:22  <rvagg>not a yak I was prepared to be shaving today
02:57:04  <refack>Worse case it can wait. It's a very limited access machine.
02:57:09  <rvagg>`Killed`
02:57:16  <rvagg>yeah, but now I don't want to update ci
02:57:22  <rvagg>if it does the same thing I'll be here forever
02:57:36  <maclover7>What's the error message
02:57:50  <rvagg>I have an appointment I'm supposed to be at so I'm going to lift the shutdown from ci.nodejs.org and let's just leave it restricted for now
02:57:55  <rvagg>will be back in an hour or two
02:58:24  <maclover7>If ci-release is no good, I'd hold on the public ci upgrade
02:58:31  <rvagg>error is `Killed`, nothing else, no log output, just that on the terminal, happens very quickly which makes me suspect a java problem
02:59:36  <rvagg>ok, cancelled shutdown
02:59:46  <rvagg>will figure this out when I'm back
03:03:47  <maclover7>Ok, cool, thanks for investigating :)
03:15:37  * Laifjoined
03:19:24  * Laifquit (Remote host closed the connection)
03:28:30  * Iota15joined
03:29:27  * marcoslaterjoined
03:30:23  * Iota15quit (Killed (Sigyn (Spam is off topic on freenode.)))
03:33:08  * marcoslaterquit (Remote host closed the connection)
03:48:29  * oso96_20000joined
03:49:45  * oso96_20000quit (Remote host closed the connection)
04:10:01  <rvagg>ok, back at it
04:10:45  <rvagg>it's amusing ... cause it was the build wg 2 weeks ago that gdams was saying that we should back up jenkins.war when upgrading .. this is failing because of jenkins.war
04:11:02  <rvagg>mind you, I could easily downgrade, and it doesn't get us the new version from upstream
04:12:25  <rvagg>hah, nope, even previous version of jenkins.war does the same thing
04:12:34  <rvagg>`java -jar jenkins.war` = immediate `Killed`
04:16:53  * Michail1joined
04:20:03  * Michail1quit (Killed (Unit193 (Spam is not permitted on freenode.)))
04:22:45  <rvagg>the plot thickens
04:22:46  <rvagg>"Out of memory: Kill process 11953 (java) score 1 or sacrifice child"
04:34:03  <rvagg>got it, downgraded kernel
04:55:47  <rvagg>https://github.com/nodejs/node/issues/22349
04:57:22  <rvagg>maclover7, refack: one of you want to undo the ci restriction now?
04:57:25  <rvagg>good to go
05:00:41  * the_madman15joined
05:05:33  * the_madman15quit (Remote host closed the connection)
05:20:05  * node-ghjoined
05:20:05  * node-ghpart
05:29:39  * mcspud29joined
05:31:31  * mcspud29quit (Remote host closed the connection)
05:44:54  * jak4joined
05:47:24  * jak4quit (Remote host closed the connection)
06:43:27  <rvagg>got it done myself
06:44:09  <rvagg>updated plugins too
06:45:41  * node-ghjoined
06:45:41  * node-ghpart
07:00:34  * guardian2joined
07:02:16  * guardian2quit (Remote host closed the connection)
07:12:49  * guest3546joined
07:12:55  * guest3546quit (Remote host closed the connection)
07:22:38  * ghormoon0joined
07:23:18  * ghormoon0quit (Remote host closed the connection)
07:56:30  * jackmcbarn24joined
07:57:48  * jackmcbarn24quit (Remote host closed the connection)
08:17:51  * cxregquit (Ping timeout: 272 seconds)
08:26:28  * cxregjoined
08:44:33  * node-ghjoined
08:44:33  * node-ghpart
09:09:45  * Guest81711joined
09:11:34  * Guest81711quit (Remote host closed the connection)
09:15:29  * lorimer0joined
09:16:46  * lorimer0quit (Remote host closed the connection)
09:28:20  * kunwon117joined
09:34:28  * kunwon117quit (Ping timeout: 272 seconds)
09:42:41  * naos9joined
09:52:13  * naos9quit (Ping timeout: 260 seconds)
10:24:11  * Cork26joined
10:33:05  * Cork26quit (Ping timeout: 240 seconds)
10:41:30  * Deusdeorum17joined
10:45:49  * Deusdeorum17quit (Remote host closed the connection)
10:48:16  * sxajoined
11:10:58  * thevdude11joined
11:12:13  * thevdude11quit (Remote host closed the connection)
12:56:48  * juggernaut_451joined
12:58:56  * juggernaut_451quit (Client Quit)
13:07:50  * TriangleSausagejoined
13:10:27  * TriangleSausagequit (Remote host closed the connection)
13:30:20  * node-ghjoined
13:30:20  * node-ghpart
13:38:44  * Guest64114joined
13:42:32  * Guest64114quit (Remote host closed the connection)
14:04:28  * talisein17joined
14:05:40  * talisein17quit (Read error: Connection reset by peer)
14:51:37  <joaocgreis>refack: https://ci.nodejs.org/computer/test-rackspace-win2008r2-x64-5/ brought it back, computers shut down in rackspace from time to time. Can I mark it as online in Jenkins? Just checking that you have no work in progress there or something.
14:52:02  <refack>Yep
14:52:19  <refack>It was just unresponsive
14:53:22  <refack>BTW: it missed the last few update Jenkins jobs
15:03:45  * node-ghjoined
15:03:45  * node-ghpart
15:18:07  * node-ghjoined
15:18:07  * node-ghpart
15:22:10  * BranchPredictor1joined
15:22:16  * richardlau_joined
15:25:13  * BranchPredictor1quit (Remote host closed the connection)
15:28:24  * ^MillerBossjoined
15:28:52  <richardlau_>I'm trying to use the VersionSelectorScript groovy script in nodereport-continuous-integration but am getting a "UnapprovedUsageException: script not yet approved for use"
15:29:10  <refack>Checking
15:29:24  <richardlau_>Thanks
15:29:37  * ^MillerBossquit (Remote host closed the connection)
15:30:32  <refack>Approved. I'm not sure what is Jenkins' policy for requiring approval...
15:31:15  <refack>P.S. make sure to add the git SCM "Extract node parameters" plugin
15:32:12  <richardlau_>What's that do?
15:33:46  <refack>I'm not sure of the mechanics, but the result is it sets `NODEJS_VERSION` and NODEJS_MAJOR_VERSION`
15:35:25  <refack>It reads `src/node_version.h` - https://github.com/nodejs/node-version-jenkins-plugin/blob/e010d2e59265524147d76848bd0b06694e464c42/src/main/java/org/nodejs/jenkinsplugins/nodeversion/NodeVersionExtension.java#L101-L116
15:35:43  <refack>So if your git repo doesn't have it, just set the env vars
15:36:46  <richardlau_>Ah node-report doesn't build node, it downloads it from the website.
15:37:14  <richardlau_>I renamed the existing parameter to NODEJS_MAJOR_VERSION
15:37:55  * node-ghjoined
15:37:55  * node-ghpart
15:48:10  * node-ghjoined
15:48:10  * node-ghpart
17:15:17  * jamesljoined
17:16:04  * jameslquit (Remote host closed the connection)
17:20:24  <richardlau_>https://nodejs.org/download/nightly/v11.0.0-nightly2018081616accff90f/ is missing headers, mac os builds
17:22:24  * richardlau_quit (Quit: Page closed)
17:22:28  * node-ghjoined
17:22:28  * node-ghpart
17:49:27  * sxaquit (Ping timeout: 240 seconds)
18:57:36  * berFt3joined
19:01:55  * berFt3quit (Remote host closed the connection)
19:50:22  * guntbert27joined
19:55:14  * guntbert27quit (Remote host closed the connection)
19:55:53  * Sitrijoined
19:59:41  * Sitriquit (Remote host closed the connection)
20:12:50  * zenguy-joined
20:17:09  * zenguy-quit (Remote host closed the connection)
20:35:45  <refack>joaocgreis mhdawson_ rvagg some release workers are offline (e.g. centos6-86 & macos10.11) - https://ci-release.nodejs.org/computer/
20:36:11  <refack>richardlau ^^^
21:31:36  * promotejoined
21:36:14  * promotequit (Remote host closed the connection)
21:52:21  * Guest72310joined
21:55:28  * Guest72310quit (Remote host closed the connection)
22:09:51  * node-ghjoined
22:09:51  * node-ghpart
22:16:10  * eido1onjoined
22:17:28  * eido1onquit (Remote host closed the connection)
22:44:44  * mfa29826joined
22:47:17  * mfa29826quit (Remote host closed the connection)