08:35:38  * BridgeARjoined
09:24:22  * seishunjoined
09:46:52  * BridgeARquit (Ping timeout: 245 seconds)
09:47:20  * BridgeARjoined
10:03:50  * node-ghjoined
10:03:50  * node-ghpart
10:25:06  * mylesborinsquit (Quit: farewell for now)
10:25:14  * mylesborinsjoined
11:43:29  * BridgeARquit (Ping timeout: 255 seconds)
13:43:14  * node-ghjoined
13:43:14  * node-ghpart
14:07:42  * BridgeARjoined
16:58:09  * seishunquit (Ping timeout: 248 seconds)
17:09:49  * seishunjoined
17:16:49  * seishunquit (Ping timeout: 248 seconds)
17:22:43  * seishunjoined
17:34:11  * BridgeARquit (Ping timeout: 265 seconds)
18:51:38  * srl295quit (Quit: Connection closed for inactivity)
19:11:39  * seishunquit (Disconnected by services)
19:11:45  * seishunjoined
19:16:15  * seishunquit (Ping timeout: 256 seconds)
19:22:41  * seishunjoined
19:37:45  * seishunquit (Ping timeout: 245 seconds)
20:52:41  * seishunjoined
21:14:20  * seishunquit (Ping timeout: 260 seconds)
22:59:48  <Trott>Is it obvious to anyone why https://ci.nodejs.org/job/node-test-commit-linuxone/2690/nodes=rhel72-s390x/console failed to build? Here's the bit I'm expecting to find the answer in but not seeing it:
22:59:50  <Trott>https://www.irccloud.com/pastebin/M8dEyTgo/
23:43:20  <rvagg>Trott: this looks like a problem we've encountered a lot in the past, "17:01:41 make[2]: write error", it doesn't have "stdout" in it though, so it may not be quite the same.
23:43:46  <rvagg>Trott: unfortunately the `make` on there doesn't seem to support the same sync stdout method so I'm not sure there's an easy fix for this except going to -j1 which would slow it right down ..