00:32:07  <mhdawson>looking for a couple of lgtms on https://github.com/nodejs/node/pull/8274, just marks a test on AIX as flaky to minimize likelyhood of build failures
00:39:42  <evanlucas>jbergstroem what ref did you use?
02:42:31  <jbergstroem>evanlucas: latest head. sorry; busy day. Happy to fix it later on
02:42:49  <evanlucas>ah interesting
02:42:57  <evanlucas>I'll take a look tomorrow
02:43:09  <jbergstroem>evanlucas: i'll try to beat you to it :)
06:27:19  * jalcinequit (Quit: ZNC - 1.6.0 - http://znc.in)
06:58:03  * jenkins-monitorquit (Remote host closed the connection)
06:58:15  * jenkins-monitorjoined
07:09:11  * jalcinejoined
10:13:01  * sgimenojoined
10:48:09  * thealphanerdquit (Quit: farewell for now)
10:48:40  * thealphanerdjoined
11:31:23  <evanlucas>um, having some build troubles on ci-release, anyone have any ideas?
11:46:18  <jbergstroem>lets see
13:03:35  * lance|afkchanged nick to lanceball
13:51:08  * node-ghjoined
13:51:09  * node-ghpart
13:51:20  * node-ghjoined
13:51:21  * node-ghpart
13:54:41  * node-ghjoined
13:54:41  * node-ghpart
13:58:50  * node-ghjoined
13:58:51  * node-ghpart
14:07:38  * sgimenoquit (Quit: Leaving)
14:13:55  * evanlucasquit (Remote host closed the connection)
14:15:47  * chorrelljoined
14:40:30  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
14:42:34  * jalcinequit (Quit: ZNC - 1.6.0 - http://znc.in)
14:45:36  * jalcinejoined
14:57:18  * evanlucasjoined
15:01:12  <evanlucas>so on the 6.5.0 release (https://ci-release.nodejs.org/job/iojs+release/1101/), OS X only has source tarballs, there are not any tarballs with the binary though?
15:14:44  <evanlucas>i'll try again and see if that helps
15:56:09  <mhdawson>FYI if you see a lot of stacked node-test-commit-aix jobs its again just because I'm trying to test out a fix for an intermittent issue
16:01:20  <Trott>For phillipj and anyone else working on the bot: This may already be on your radar, but if not, there's a feature I really like (so far, anyway) that the eslint repo uses where a bot looks at a PR and makes an educated guess about who to loop in for a review. Here's an example comment: https://github.com/eslint/eslint/pull/6981#issuecomment-242689628
16:19:45  * Fishrock123joined
17:00:13  * node-ghjoined
17:00:13  * node-ghpart
17:32:48  <jbergstroem>evanlucas: perhaps give it another run
17:33:52  <jbergstroem>Trott: perhaps open an issue about it at github.com/nodejs/github-bot ?
17:43:17  <phillipj>Trott: I've been thinking we could base that on the labelling logic we have.. https://github.com/nodejs/github-bot/issues/49
17:49:52  <jbergstroem>phillipj: maintainers and/or groups even
17:50:09  <jbergstroem>We could alternatively use the assigned system but we havent really touched that in the nodejs-ecosystem so far
17:58:23  <jbergstroem>heads up: using getconf for core/processor count from jenkins is unfortunately unreliable. Most vm's should have JOBS= defined now, so you shouldn't have to pass it
19:03:27  <evanlucas>jbergstroem got it working
19:03:28  <evanlucas>thanks
19:03:56  <jbergstroem>evanlucas: good!
19:49:16  * jenkins-monitorquit (Remote host closed the connection)
19:49:29  * jenkins-monitorjoined
20:04:19  * rvaggquit (Ping timeout: 260 seconds)
20:04:39  * chorrelljoined
20:04:40  * ofrobotsquit (Ping timeout: 264 seconds)
20:07:27  * benglquit (Ping timeout: 250 seconds)
20:14:05  <Trott>Can we get AIX added to the node-stress-single-test task? joaocgreis mhdawson
20:25:36  * Fishrock123quit (Quit: Leaving...)
20:35:42  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
20:39:48  * rvaggjoined
20:50:59  * evanlucasquit (Ping timeout: 260 seconds)
20:53:38  * ofrobotsjoined
21:03:32  * bengljoined
21:06:47  <jbergstroem>ok
21:07:13  <jbergstroem>slave looks offline
21:07:16  <jbergstroem>lets fix that first
21:08:38  <jbergstroem>Trott: mhdawson took it out of commission for a bit; lets wait for that.
21:09:52  <mhdawson>I currently testing another fix once we get AIX back into the regular ci run I can look at the stress job
21:10:02  <jbergstroem>cool
21:16:00  * node-ghjoined
21:16:00  * node-ghpart
21:16:51  * node-ghjoined
21:16:52  * node-ghpart
21:18:35  * node-ghjoined
21:18:36  * node-ghpart
21:19:48  * node-ghjoined
21:19:49  * node-ghpart
21:20:13  * node-ghjoined
21:20:14  * node-ghpart
21:22:13  * node-ghjoined
21:22:13  * node-ghpart
21:22:31  * lanceballchanged nick to lance|afk
21:25:19  * node-ghjoined
21:25:20  * node-ghpart
21:30:01  * node-ghjoined
21:30:02  * node-ghpart
21:38:10  <Trott>Windows build failure. https://ci.nodejs.org/job/node-stress-single-test/860/nodes=win2012r2-1p/console "stderr: warning: failed to remove deps/openssl/Release/obj/openssl/openssl.pdb" joaocgreis
21:41:52  <jbergstroem>:/
21:58:17  * evanlucasjoined
22:00:08  * node-ghjoined
22:00:08  * node-ghpart
22:18:38  <Trott>Another (different?) Windows failure: "FATAL: Command "git clean -fdx" returned status code 1:" at https://ci.nodejs.org/job/node-stress-single-test/863/nodes=win2012r2-1p/console
22:18:57  <jbergstroem>yeah
22:19:04  <jbergstroem>i can't for hte love of god figure those out
22:19:20  <Trott>And here too: https://ci.nodejs.org/job/node-stress-single-test/863/nodes=win10-1p/console
22:19:26  <Trott>Bummer. OK.
22:20:25  <jbergstroem>joaocgreis: intenret talks about path_max issues -- is that really the case? http://stackoverflow.com/questions/35855496/git-clean-or-reset-fails-on-windows-10
22:35:03  * jenkins-monitorquit (Excess Flood)
22:35:11  * jenkins-monitorjoined
23:02:57  * ofrobotsquit (Ping timeout: 250 seconds)
23:03:28  * rvaggquit (Ping timeout: 264 seconds)
23:15:03  * ofrobotsjoined
23:32:33  * rvaggjoined
23:36:29  * orangemochaquit (Ping timeout: 244 seconds)
23:36:56  * orangemochajoined
23:46:03  * ofrobotsquit (Remote host closed the connection)
23:46:04  * rvaggquit (Remote host closed the connection)
23:46:04  * benglquit (Remote host closed the connection)