01:08:00  * jaywonquit (Remote host closed the connection)
01:41:37  * jaywonjoined
01:45:51  * jaywonquit (Ping timeout: 240 seconds)
01:46:39  * node-ghjoined
01:46:39  * node-ghpart
01:53:06  * node-ghjoined
01:53:07  * node-ghpart
02:45:36  * jaywonjoined
02:53:51  * jaywonquit (Ping timeout: 240 seconds)
02:58:28  * jaywonjoined
03:02:51  * jaywonquit (Ping timeout: 240 seconds)
03:05:01  * jaywonjoined
03:37:54  * jaywon_joined
03:41:19  * jaywonquit (Ping timeout: 260 seconds)
04:24:49  * jaywon_quit (Remote host closed the connection)
04:37:46  * jaywonjoined
05:14:10  * jaywon_joined
05:17:47  * jaywonquit (Ping timeout: 276 seconds)
06:00:31  * jaywon_quit (Remote host closed the connection)
06:01:01  * jaywonjoined
06:01:04  * jaywonquit (Remote host closed the connection)
06:01:39  * jaywonjoined
06:06:21  * jaywonquit (Ping timeout: 264 seconds)
06:18:13  * jaywonjoined
06:55:28  * jaywonquit (Remote host closed the connection)
06:56:05  * jaywonjoined
07:00:34  * jaywonquit (Ping timeout: 244 seconds)
07:02:39  * jaywonjoined
07:06:51  * jaywonquit (Ping timeout: 240 seconds)
07:54:31  * jaywonjoined
07:59:39  * jaywonquit (Ping timeout: 276 seconds)
08:33:48  * seishunjoined
08:46:09  * node-ghjoined
08:46:09  * node-ghpart
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:18  * mylesborinsjoined
10:38:08  * jaywonjoined
10:42:21  * jaywonquit (Ping timeout: 240 seconds)
11:20:32  * jaywonjoined
11:25:01  * jaywonquit (Ping timeout: 265 seconds)
12:21:19  * node-ghjoined
12:21:19  * node-ghpart
12:34:52  <maclover7>rvagg: It looks like there might be a networking issue with the Pi machines right now
12:35:00  <maclover7>A whole bunch of them are offline (http://node-build-monitor.herokuapp.com/)
12:35:20  <maclover7>https://www.irccloud.com/pastebin/NnZ9Ccwu/
12:35:26  <maclover7>^ and getting this error when trying to SSH in
12:35:37  <maclover7>`ssh -i ~/.ssh/nodejs_build_test -p 2222 jump@vagg-arm.nodejs.org` works though
12:51:30  * node-ghjoined
12:51:30  * node-ghpart
12:51:57  * node-ghjoined
12:51:57  * node-ghpart
12:52:05  * node-ghjoined
12:52:05  * node-ghpart
12:52:34  * seishunquit (Ping timeout: 260 seconds)
12:57:11  * node-ghjoined
12:57:11  * node-ghpart
13:05:09  * jaywonjoined
13:10:20  * jaywonquit (Ping timeout: 276 seconds)
13:28:58  <rvagg>maclover7: yeah, so we're having some big 'ol problems in my network and I'm not there right now to sort it out. I've taken arm-fanned out of test-commit so they shouldn't hold things up and I'll try and get it at least partially sorted out as soon as I can.
13:29:23  <rvagg>thankfully releases for 10+ don't rely on that cluster any more, except for testing, which is important but not critical
13:30:46  <rvagg>ugh, even the mac mini is down, mhdawson_ how's that new release machine setup going? might be needing it sooner than later
13:31:22  <rvagg>btw, I'm on vacation and not physcially there and there are problems that are difficult to solve with someone over the phone
13:33:31  <maclover7>rvagg: Ok, no problem
13:34:18  <maclover7>Also, I just got back from taking about a week and a half vacation, don't feel bad for taking a break :)
13:34:37  <maclover7>Just wanted to raise issue so wouldn't fall by the wayside
13:41:38  <rvagg>ok, I figured out a way to get the mac machines back online, so minor crisis averted, we have osx release back
13:41:52  <rvagg>the only thing we can't do just now is release armv6 older than Node 10
13:42:29  <refack>If we don't have the macos setup then AFAICT no mac or tarball release as well?
13:42:48  <refack>Ohh ok
13:43:40  <refack>Was about to post a headsup to the release group, but stretching that
13:44:55  <rvagg>I'll let y'all know if there are any developments, but potentially the pi's could be down till the end of the week
13:45:21  <rvagg>got a UPS that decided to give up the day after I left the house
13:45:51  <rvagg>causing havoc on the network and one of my attempts to improve the situation has made it worse by taking a critical machine offline ..
13:46:10  <refack>Murphy's law rears its ugly head. Again.
13:47:21  <rvagg>yeah, amazing timing tbh, everything's been going so well
13:47:40  <rvagg>anyway, I really need this vacation so I have to make the most of it and try not stress about this
13:48:47  <refack>(My biggest beef with UPS technology, if that most of it is upconverting the batteries' 12V to 220V [with lousy capacitors], then all the hardware works hard to down convert it back to 12V)
13:49:10  <maclover7>No worries, enjoying your vacation :)
13:49:34  <maclover7>For whenever you get back, sounds like it might make sense to try and get foundation $$ to better stabilize the pi machines
15:37:05  <Trott>Any chance we can get a win10 machine in node-stress-single-test that build against master. The only one we have is win10-1p-vs2015 which gives output like https://ci.nodejs.org/job/node-stress-single-test/nodes=win10-1p-vs2015/1932/console which suggests to me that we need vs2017?
15:48:18  * node-ghjoined
15:48:19  * node-ghpart
15:49:21  * seishunjoined
15:51:48  * node-ghjoined
15:51:49  * node-ghpart
15:53:51  * seishunquit (Ping timeout: 240 seconds)
16:09:24  <refack>Trott: I'll try to set up one
16:09:50  <Trott>❤️
16:27:05  * node-ghjoined
16:27:05  * node-ghpart
16:42:57  * jaywonjoined
16:47:24  * jaywonquit (Ping timeout: 265 seconds)
17:11:40  <refack>https://www.irccloud.com/pastebin/M9jVnyyG/
17:11:48  <refack>Trott: PTAL https://ci.nodejs.org/job/node-stress-single-test/build?delay=0sec,
17:11:49  <refack>* Switched label selector to checkboxes (notice the checkboxes are AFTER the labels)
17:11:49  <refack>* Added `win10-vs2017` but it's kind of a jalopy; 1 cpu core and 4GB RAM
17:12:02  <refack>Now running https://ci.nodejs.org/job/node-stress-single-test/1938/nodes=win10-vs2017/console
17:15:13  <mhdawson_>@rvagg, at least my plan for the the new OSX machine was only to build on master + , so your mini being down would still have been an issue, good to hear you have it back
17:15:39  <mhdawson_>I guess we should start a discussion if we should move the rest of the releases to a MacStadium 1010 machine, but still have a few reservations that we have discussed
17:17:57  * node-ghjoined
17:17:57  * node-ghpart
17:21:31  <Trott>Thanks, refack! I can't do much with it yet because node-stress-single-test is throttled to one test at a time. But I'm stoked to give it a try later!
17:21:56  <Trott>Also: jalopy = good for stress tests. Makes it easier to replicate problems. :-D
17:22:26  <refack>Yeah I guess, just so you are aware
17:24:57  * node-ghjoined
17:24:57  * node-ghpart
17:25:25  * jaywonjoined
17:29:21  * jaywonquit (Ping timeout: 240 seconds)
18:57:44  * jaywonjoined
19:02:12  * jaywonquit (Ping timeout: 256 seconds)
19:48:48  * jaywonjoined
20:17:46  * jaywonquit (Remote host closed the connection)
20:18:24  * jaywonjoined
20:23:14  * jaywonquit (Ping timeout: 276 seconds)
20:40:28  * node-ghjoined
20:40:28  * node-ghpart
20:42:12  * jaywonjoined
21:00:34  * jaywonquit (Remote host closed the connection)
21:09:38  * jaywonjoined
21:23:14  * jaywon_joined
21:27:35  * jaywonquit (Ping timeout: 276 seconds)
21:58:35  * node-ghjoined
21:58:35  * node-ghpart
22:00:10  * node-ghjoined
22:00:10  * node-ghpart
22:02:44  <mmarchini>https://zoom.us/j/715960833 is that the link for the meeting?
22:06:34  * node-ghjoined
22:06:34  * node-ghpart
22:11:34  * amiller-ghjoined
22:16:07  * sgimenoquit (Ping timeout: 256 seconds)
22:18:26  * sgimenojoined
22:37:51  * amiller-ghquit (Ping timeout: 252 seconds)
23:06:01  * node-ghjoined
23:06:01  * node-ghpart
23:27:24  * jaywon_quit (Ping timeout: 244 seconds)
23:29:08  * jaywonjoined
23:30:17  * jaywonquit (Remote host closed the connection)
23:30:54  * jaywonjoined
23:35:09  * jaywonquit (Ping timeout: 244 seconds)