00:10:04  * Fishrock123quit (Remote host closed the connection)
00:12:50  * Fishrock123joined
00:20:20  * sgimeno_joined
00:22:59  * sgimeno__quit (Ping timeout: 258 seconds)
01:09:36  * Fishrock123quit (Remote host closed the connection)
01:10:41  * Fishrock123joined
01:12:52  * node-ghjoined
01:12:52  * node-ghpart
01:15:49  * node-ghjoined
01:15:49  * node-ghpart
01:16:39  * Fishrock123quit (Remote host closed the connection)
01:19:16  * Fishrock123joined
01:26:25  * Fishrock123quit (Remote host closed the connection)
01:57:37  * Fishrock123joined
02:02:16  * Fishrock123quit (Remote host closed the connection)
02:16:52  * sgimeno__joined
02:16:57  * sgimeno_quit (Ping timeout: 240 seconds)
02:21:40  * Fishrock123joined
02:33:07  * Fishrock123quit (Quit: Leaving...)
02:44:53  * maclover7quit (Quit: Leaving.)
03:01:12  * sgimeno_joined
03:03:29  * sgimeno__quit (Ping timeout: 248 seconds)
03:15:09  * sgimeno__joined
03:17:53  * sgimeno_quit (Ping timeout: 248 seconds)
04:14:57  * sgimeno__quit (Ping timeout: 240 seconds)
06:12:46  * sgimenojoined
06:16:32  * seishunjoined
06:20:37  * sgimenoquit (Ping timeout: 260 seconds)
06:21:41  * sgimenojoined
06:26:59  * sgimenoquit (Ping timeout: 246 seconds)
06:31:39  * node-ghjoined
06:31:39  * node-ghpart
06:34:08  * node-ghjoined
06:34:08  * node-ghpart
06:59:21  <Trott>Linux jobs seem to be stalled. I guess that's what the "hurricane in Ireland, servers down" stuff is about above? Should we temporarily remove ubuntu1604-intel-64 so that node-test-commit-linux can finish?
07:34:23  * seishunquit (Ping timeout: 248 seconds)
07:45:40  * joyeejoined
08:23:50  * joyeequit (Remote host closed the connection)
09:15:59  * joyeejoined
09:16:21  * node-ghjoined
09:16:21  * node-ghpart
09:18:43  * node-ghjoined
09:18:43  * node-ghpart
09:19:48  * node-ghjoined
09:19:48  * node-ghpart
09:26:26  * joyeequit (Remote host closed the connection)
09:37:31  * joyeejoined
09:40:57  * joyeequit (Remote host closed the connection)
09:46:32  * joyeejoined
10:17:34  * node-ghjoined
10:17:34  * node-ghpart
10:25:12  * mylesborinsquit (Quit: farewell for now)
10:25:42  * mylesborinsjoined
10:40:55  * joyeequit (Remote host closed the connection)
10:41:23  * joyeejoined
10:45:57  * joyeequit (Ping timeout: 240 seconds)
11:02:23  * maclover7joined
11:07:38  * node-ghjoined
11:07:38  * node-ghpart
11:17:12  * node-ghjoined
11:17:12  * node-ghpart
11:19:15  * maclover7quit (Quit: Leaving.)
11:35:05  * node-ghjoined
11:35:05  * node-ghpart
11:42:05  * node-ghjoined
11:42:05  * node-ghpart
11:42:43  * node-ghjoined
11:42:43  * node-ghpart
11:52:45  * node-ghjoined
11:52:45  * node-ghpart
12:05:03  * maclover7joined
12:06:05  * joyeejoined
12:06:28  * node-ghjoined
12:06:28  * node-ghpart
12:08:11  * node-ghjoined
12:08:11  * node-ghpart
12:09:33  * node-ghjoined
12:09:33  * node-ghpart
12:15:59  * node-ghjoined
12:15:59  * node-ghpart
12:16:03  * maclover7quit (Quit: Leaving.)
12:17:28  * node-ghjoined
12:17:28  * node-ghpart
12:17:49  * node-ghjoined
12:17:49  * node-ghpart
12:23:36  <joyee>Hi, does anyone know what's different in the linux-fips core test setup? Modifying build-ci target of the Makefile of core doesn't seem to take effect there
12:30:07  <rvagg>joyee: yeah, normal linux does this to run the build & test: NODE_TEST_DIR=${HOME}/node-tmp PYTHON=python FLAKY_TESTS=$FLAKY_TESTS_MODE make run-ci -j $(getconf _NPROCESSORS_ONLN)
12:31:03  <rvagg>joyee: but linux-fips does a manual `./configure`, `make -j ...` and then `make test-ci`, so `build-ci` is missing from that process
12:31:26  <joyee>Got it, thanks
12:32:27  <rvagg>joyee: here's the actual differences: https://gist.github.com/rvagg/38f951a4d41bc3f83137b8845e53f788
12:32:57  <joyee>awesome, thank you
12:33:24  <rvagg>joyee: if you want to propose a change to any of that then let us know, myself, Michael, joaocgreis or jbergstroem can make the change in there (maybe a few others have access). Nothing is particularly sacred in there, as long as it "just works" then change what you need.
12:34:06  <joyee>I think I can just put my changes in test-ci and it will work
12:34:28  <rvagg>ok, if it's that easy then that's great!
12:34:46  <joyee>:)
12:37:45  * node-ghjoined
12:37:45  * node-ghpart
12:46:02  <joyee>The benchmark CI machine seems to be offline, is it being maintained?
12:46:08  <joyee>https://ci.nodejs.org/computer/test-nearform_intel-ubuntu1604-x64-1/
12:47:25  <rvagg>joyee: yeah, no power in Ireland where they are hosted, hurricane kind of messed up the place
12:47:36  <joyee>0-0
12:47:43  <joyee>that's terrible
12:47:52  <joyee>anyway thanks for the response
12:48:25  <rvagg>joyee: yeah, best cancel any jobs that run there, I've taken them out of the node-test-linux mix but they probably shouldn't be in there anyway (I think)
12:48:56  <joyee>got it, thanks
13:26:25  * maclover7joined
13:26:35  * maclover7quit (Client Quit)
13:29:31  * lance|afkchanged nick to lanceball
14:13:14  * node-ghjoined
14:13:14  * node-ghpart
14:43:11  * joyeequit (Remote host closed the connection)
14:46:42  * joyeejoined
14:49:18  * joyeequit (Remote host closed the connection)
15:19:52  * joyeejoined
15:24:27  * joyeequit (Ping timeout: 240 seconds)
15:36:41  * joyeejoined
15:48:45  * seishunjoined
17:11:17  * joyee_joined
17:12:05  * joyeequit (Ping timeout: 240 seconds)
20:16:14  * node-ghjoined
20:16:14  * node-ghpart