00:01:08  <evanlucas>mhdawson_ do I need to update the banner on the website?
00:05:08  <evanlucas>maclover7 release is out
00:05:21  <evanlucas>Anything special I need to do when landing the blog posts PRs?
00:05:56  <mhdawson_>I'll update the banner as part of the update to the blog post announcing the vulnerabilities
00:06:15  <evanlucas>ok cool, thanks!
00:06:45  <mhdawson_>will send that PR in a few minutes after I get the PR for the docker images sent and send out the announce to nodejs-sec
00:16:30  <mylesborins>evanlucas you are a champ!!!
00:16:58  <evanlucas>thanks. huge shout out to build wg
00:20:03  <mylesborins>woot
00:20:39  <mhdawson_>still working on announce PR, need to fixu up a few things, also problem with getting docker images out as I need an approval which was unexpected
00:20:58  <mhdawson_>are the changelogs published yet
00:21:30  <mhdawson_>Evan
00:21:41  <mhdawson_>So I might have added some confusion
00:21:56  <mhdawson_>I'm going to update the banner and a blog with the security release announce
00:22:08  <mhdawson_>but still need you do to the blogs for each release.
00:22:15  <mhdawson_>but I guess maybe there are PRs for those, looking
00:22:17  <mylesborins>I can do that quickly
00:22:38  <mylesborins>oh nvm they are there
00:22:39  <mylesborins>https://github.com/nodejs/nodejs.org/commit/fdd980478193b68fcaf2609b377b8001b80403f4
00:23:44  <mhdawson_>maybe my links are stale or the website has not updated yet
00:24:26  <mhdawson_>good now just tooks a few minutes to update
00:24:28  <refack>https://nodejs.org/en/blog/?a=1 It's up
00:24:48  <mhdawson_>PR for announce here
00:24:49  <mhdawson_>https://github.com/nodejs/nodejs.org/pull/1692
00:24:56  <mhdawson_>going to send to nodejs-sec
00:25:20  <ljharb>so why v9 but not v7 or v5 or v4?
00:25:31  <ljharb>isn't v9 EOL the instant v10 comes out? or am i misremembering the schedule
00:27:23  * BridgeAR1quit (Ping timeout: 265 seconds)
00:27:42  <mylesborins>ljharb we offer maintenance until end of june
00:27:56  <ljharb>ah k, ty
00:29:45  <mylesborins>merged sec post
00:36:46  <mhdawson_>ok message send to nodejs-sec
00:36:49  <mhdawson_>on to docker images
00:39:50  * jaywonquit (Remote host closed the connection)
00:40:27  * jaywonjoined
00:42:43  * jaywon_joined
00:45:02  * jaywonquit (Ping timeout: 276 seconds)
00:47:38  * jaywon_quit (Ping timeout: 276 seconds)
00:54:12  * evanlucasquit (Remote host closed the connection)
00:55:55  <mylesborins>did someone make a change to the CI job?
00:56:07  <mylesborins>it is defaulting to 8.x for the PR base branch 🤔
00:56:09  <mhdawson_>Jon had modified before
00:56:17  <mhdawson_>to work with the private repo
00:56:22  <mhdawson_>he was going to change back afterwards
00:56:25  <mylesborins>https://ci.nodejs.org/job/node-test-pull-request/15426/
00:56:26  <mhdawson_>not sure if its related to that
00:57:06  <mylesborins>hmmm
00:57:07  <mylesborins>I manually fixed it for the one CI job I had to do
00:57:08  <mylesborins>but something is wrong there
00:58:18  <refack>I rolled it back
01:13:26  * jaywonjoined
01:26:47  <maclover7>mylesborins: refack: mhdawson_: looks like someone fixed it up, should be good now
01:27:32  * node-ghjoined
01:27:32  * node-ghpart
01:34:18  <maclover7>FYI, rolled out `node-test-commit-test` unified script to freebsd and linuxone
01:34:26  <maclover7>If all goes well will continue to roll out over next few days
01:34:34  <maclover7>Had tested on private jobs and seemed fine
02:02:05  <Trott>What is `node-test-commit-test`?
02:04:07  <maclover7>https://github.com/nodejs/build/pull/1329
02:04:24  <maclover7>I'm slowing trying to centralize the Jenkins scripts we use in the node-test-pull-request sub jobs
02:04:36  <maclover7>To try and make it easier to maintain and stuff
02:04:39  <maclover7>And to be track in git :)
02:13:38  * jaywonquit (Remote host closed the connection)
02:13:46  * jaywonjoined
02:17:45  * jaywonquit (Remote host closed the connection)
02:41:27  * jaywonjoined
02:46:20  * gabrielschulhofquit (Ping timeout: 268 seconds)
02:57:20  * jaywonquit (Remote host closed the connection)
02:57:47  * jaywonjoined
03:02:26  * jaywonquit (Ping timeout: 260 seconds)
03:03:58  * jaywonjoined
03:10:26  * jaywonquit (Remote host closed the connection)
03:21:17  * jaywonjoined
04:42:25  * jaywon_joined
04:45:37  * jaywonquit (Ping timeout: 245 seconds)
07:16:43  * jaywonjoined
07:20:14  * jaywon_quit (Ping timeout: 276 seconds)
07:25:29  * srl295quit (Quit: Connection closed for inactivity)
08:00:04  * jaywonquit (Remote host closed the connection)
08:00:57  * jaywonjoined
08:05:37  * jaywonquit (Ping timeout: 256 seconds)
08:12:07  * node-ghjoined
08:12:07  * node-ghpart
08:12:20  * node-ghjoined
08:12:20  * node-ghpart
08:13:47  * node-ghjoined
08:13:47  * node-ghpart
08:19:33  * seishunjoined
09:41:48  * amiller-ghjoined
10:02:54  * amiller-ghquit (Ping timeout: 260 seconds)
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:40  * mylesborinsjoined
10:34:50  * sxajoined
10:36:01  * BridgeAR1joined
10:40:53  * seishunquit (Read error: Connection reset by peer)
10:41:27  * seishunjoined
10:55:58  * sxaquit (Remote host closed the connection)
11:24:03  * sxajoined
11:35:28  * gabrielschulhofjoined
11:37:10  * node-ghjoined
11:37:10  * node-ghpart
12:02:59  * node-ghjoined
12:02:59  * node-ghpart
12:38:21  * sxaquit (Quit: Leaving)
13:13:56  * node-ghjoined
13:13:56  * node-ghpart
13:37:02  * node-ghjoined
13:37:02  * node-ghpart
13:42:51  * node-ghjoined
13:42:51  * node-ghpart
13:49:07  * node-ghjoined
13:49:07  * node-ghpart
13:54:41  * node-ghjoined
13:54:41  * node-ghpart
14:01:51  * node-ghjoined
14:01:51  * node-ghpart
14:34:02  * node-ghjoined
14:34:02  * node-ghpart
14:34:24  * node-ghjoined
14:34:24  * node-ghpart
14:34:50  * node-ghjoined
14:34:50  * node-ghpart
14:35:10  * node-ghjoined
14:35:10  * node-ghpart
14:37:59  <joyee>maclover7 refack If you are around...can you check that I can perform the actions in https://github.com/nodejs/build/issues/1331#issuecomment-396250757 without breaking any ACL? My guess is that I won't because the teams will still be there.
14:38:40  <joyee>Also for merging release admins into infra admins, I can delete the section from README but only someone with their keys in those folders can merge the folders
14:40:09  <refack>IMHO refactoring the teams should be OK.
14:40:30  * node-ghjoined
14:40:30  * node-ghpart
14:40:33  <refack>Ping when you do it and I'll just test if I can still access the admin interfaces
14:40:38  * node-ghjoined
14:40:38  * node-ghpart
14:42:40  * node-ghjoined
14:42:40  * node-ghpart
14:43:43  <joyee>refack: I've done it, please take a look at the Jenkins, thanks
14:45:04  * node-ghjoined
14:45:04  * node-ghpart
14:45:10  <refack>joyee: all good on my end
14:45:26  <joyee>good
14:48:37  * node-ghjoined
14:48:37  * node-ghpart
15:03:29  <mylesborins>maclover7 I just noticed you are in NYC
15:04:08  <mylesborins>have you ever gone to the borojs meetups?
15:13:24  * node-ghjoined
15:13:25  * node-ghpart
15:16:41  * BridgeAR1quit (Ping timeout: 276 seconds)
15:59:11  * node-ghjoined
15:59:11  * node-ghpart
16:06:54  * BridgeAR1joined
16:37:56  * juggernaut451joined
16:46:30  * juggernaut451quit (Remote host closed the connection)
16:49:01  * juggernaut451joined
17:06:09  <maclover7>mylesborins: yup I
17:06:12  <maclover7>'m in NYC
17:06:17  <maclover7>haven't been to any of the borojs meetups before
17:09:15  * juggernaut451quit (Remote host closed the connection)
17:11:41  * node-ghjoined
17:11:41  * node-ghpart
17:24:18  <mylesborins>maclover7 we should try and go to the same one at some time!
17:24:19  <mylesborins>or alternatively you should come by google for lunch some time
17:33:58  * seishunquit (Ping timeout: 264 seconds)
17:34:48  <maclover7>mylesborins cool cool
17:35:11  <maclover7>borojs is the brooklynjs family of events right
17:35:24  <maclover7>re: google, i'm out of school next week so may have some time to come in
17:41:14  * seishunjoined
17:45:08  * Fishrock123joined
17:54:21  * sgimenoquit (Ping timeout: 240 seconds)
17:54:40  * sgimenojoined
18:02:32  * Fishrock123quit (Remote host closed the connection)
18:13:51  * Fishrock123joined
18:24:22  * BridgeAR1quit (Ping timeout: 264 seconds)
18:56:52  * jaywonjoined
18:58:14  * jaywonquit (Client Quit)
18:59:08  * node-ghjoined
18:59:08  * node-ghpart
19:24:55  <Fishrock123>heya, is anyone here able to give me perms to activate the libuv ci jobs?
19:25:08  <refack>1 sec
19:32:31  * node-ghjoined
19:32:31  * node-ghpart
19:33:06  <refack>Fishrock123: try now https://ci.nodejs.org/view/libuv/job/libuv-test-commit/
19:34:58  <Fishrock123>refack: Thanks!!
19:35:22  <ryzokuken>https://ci.nodejs.org/job/node-test-binary-windows/18000/ keeps failing for me.
19:35:25  <ryzokuken>PTAL?
19:37:41  <refack>ryzokuken: any context on this? when was it triggered? Did you try to rebuild or resume?
19:38:20  <ryzokuken>I resumed after it failed a few minutes ago.
19:38:29  <ryzokuken>resumed it's parent*
19:38:42  <refack>Ahh, windows-fanned can't be resumed
19:38:55  <refack>but I started a subjob
19:39:07  <refack>https://ci.nodejs.org/job/node-test-commit-windows-fanned/18728/
19:40:56  <refack>(
19:40:57  <refack>the job is split in two. First compile -> push binaries to git -> test -> delete binaries from git
19:40:57  <refack>even if the tests fail the git branch is deleted, so you can't resume, because Jenkins thinks it only needs to run the test sub job, since the compilation is green
19:40:57  <refack>)
19:41:39  * qbitquit (Quit: WeeChat 2.1)
19:47:40  <ryzokuken>refack gotcha
20:07:50  * qbitjoined
20:08:14  * qbitchanged nick to Guest58720
20:09:10  * seishunquit (Ping timeout: 260 seconds)
20:09:32  * Guest58720changed nick to qbit
20:34:09  * srl295joined
20:36:31  <ryzokuken>refack failed again: https://ci.nodejs.org/job/node-test-commit-windows-fanned/18728/ :(
20:37:22  <ryzokuken>Java error: https://ci.nodejs.org/job/node-test-binary-windows/18003/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console
20:37:29  <refack>ryzokuken: you can assume it's a flake
20:37:33  <ryzokuken>looks like the infra is getting flakier too :/
20:37:39  <refack>you got enough coverage
20:37:53  <ryzokuken>refack I do, because that backport won't fail anything.
20:37:58  <ryzokuken>plus it's a backport, so...
20:39:00  <refack>The git in build workspace was "locked" (probably a previous job was ABORTED during a git operation)
20:39:18  <refack>I cleaned the workspace so the machine should be back to normal
20:41:45  <ryzokuken>refack should I try rebuilding the job?
20:42:14  <refack>IMO not necessary. I can comment on the PR
20:45:29  * node-ghjoined
20:45:29  * node-ghpart
20:46:04  * node-ghjoined
20:46:04  * node-ghpart
20:47:36  * node-ghjoined
20:47:36  * node-ghpart
20:48:43  <ryzokuken>refack please do.
20:52:09  * node-ghjoined
20:52:09  * node-ghpart
20:55:19  * node-ghjoined
20:55:19  * node-ghpart
20:55:39  * node-ghjoined
20:55:39  * node-ghpart
21:07:15  * Fishrock123quit (Remote host closed the connection)
21:28:26  * seishunjoined
21:38:07  * node-ghjoined
21:38:07  * node-ghpart
21:44:30  * node-ghjoined
21:44:30  * node-ghpart
21:44:42  * seishunquit (Ping timeout: 268 seconds)
22:01:12  * Fishrock123joined
23:10:48  * Fishrock123quit (Quit: Leaving...)
23:17:59  * node-ghjoined
23:17:59  * node-ghpart
23:21:02  * node-ghjoined
23:21:02  * node-ghpart
23:28:54  * node-ghjoined
23:28:55  * node-ghpart
23:44:19  * node-ghjoined
23:44:19  * node-ghpart