06:33:43  * sgimenoquit (Ping timeout: 256 seconds)
07:29:11  * sgimenojoined
07:39:51  * seishunjoined
07:44:32  * sgimenoquit (Ping timeout: 276 seconds)
07:50:20  * sgimenojoined
08:34:09  * node-ghjoined
08:34:09  * node-ghpart
08:39:57  * seishunquit (Ping timeout: 240 seconds)
08:56:41  * targosjoined
11:11:01  * node-ghjoined
11:11:01  * node-ghpart
11:25:10  * mylesborinsquit (Quit: farewell for now)
11:25:41  * mylesborinsjoined
13:48:27  * qbitquit (Quit: WeeChat 2.0)
14:34:07  * qbitjoined
15:34:37  * Fishrock123joined
16:34:08  * node-ghjoined
16:34:08  * node-ghpart
16:51:53  <Trott>Never know what to do with failures like this: https://ci.nodejs.org/job/node-test-commit-plinux/14463/nodes=ppcle-ubuntu1404/console Haven't *really* seen that before, but you know, these "failed in some weird way I haven't noticed before" failures are also really common....
16:57:40  * chorrelljoined
17:26:13  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:30:01  * seishunjoined
18:31:29  * chorrelljoined
18:54:12  * Fishrock123quit (Remote host closed the connection)
18:54:53  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:58:20  * Fishrock123joined
19:50:00  * Fishrock123quit (Remote host closed the connection)
20:02:57  * Fishrock123joined
20:54:57  * seishunquit (Ping timeout: 265 seconds)
21:47:26  * seishunjoined
22:15:53  * Fishrock123quit (Remote host closed the connection)
22:18:55  * seishunquit (Ping timeout: 256 seconds)
22:25:53  * Fishrock123joined
23:33:20  * Fishrock123quit (Quit: Leaving...)
23:53:33  <rvagg>my guess is that the error there isn't about leaking file descriptors, something else went wrong that we're not seeing and that leak message is just a symptom. Sadly I can't see anything else, the stdout cutoff is the most odd thing.