01:35:56  * jgiquit (Quit: jgi)
01:39:10  * bnoordhuisquit (Ping timeout: 272 seconds)
01:56:46  * Fishrock123quit (Quit: Leaving...)
04:45:57  * jgijoined
04:51:08  * node-ghjoined
04:51:09  * node-ghpart
05:44:28  * node-ghjoined
05:44:29  * node-ghpart
06:48:36  * jgiquit (Quit: jgi)
06:49:08  * jgijoined
07:05:59  * jgiquit (Quit: jgi)
08:06:40  * rmgquit (Remote host closed the connection)
08:07:14  * rmgjoined
08:11:46  * rmgquit (Ping timeout: 250 seconds)
10:17:19  <jbergstroem>ok, got upstart running on ubuntu with respawn checks
10:17:28  <jbergstroem>should make osuosl stuff slightly less bouncy
10:29:28  * bnoordhuisjoined
10:30:44  <jbergstroem>orangemocha: do we really need to restart machines after each run? wouldn't clleaning directories and killing processes go a long way?
10:51:42  * imjacobclarkjoined
11:08:28  * rmgjoined
11:13:05  * rmgquit (Ping timeout: 260 seconds)
12:17:34  * imjacobclarkquit (Ping timeout: 272 seconds)
12:22:40  * bnoordhuisquit (Ping timeout: 245 seconds)
12:23:05  * bnoordhuisjoined
12:26:25  * node-ghjoined
12:26:25  * node-ghpart
12:51:11  * bnoordhuisquit (Ping timeout: 264 seconds)
13:32:57  <orangemocha>jbergstroem killing processes would certainly help. Rebooting is the ultimate catch all though. We don't know all the processes that need to be killed
13:34:09  <orangemocha>in another CI system I worked on before, rebooting was the single best cure for flakiness.
13:34:44  <orangemocha>do you see any issues with rebooting? Other that it's difficult to do with Jenkins..?
13:49:52  <orangemocha>imjacobclark, I am afraid we don't have a well defined onboarding document or process
13:50:24  <orangemocha>this is one definition of the group charter: https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#build
13:50:55  <orangemocha>the best way to get an idea of the things we deal with is probably to review https://github.com/nodejs/build/issues
13:53:20  <orangemocha>I think most participants in this group have first been contributors to https://github.com/nodejs/node. I don't know that it's a strict requirement, though there are certain security concerns why we want to known and trust someone before we give them access to the infrastructure
13:53:58  <orangemocha>can you tell us a bit more about your interest in this project?
13:54:35  <orangemocha>also ping rvagg in case I missed anything here ^
13:56:45  * imjacobclarkjoined
14:19:16  * node-ghjoined
14:19:16  * node-ghpart
14:34:23  * imjacobclarkquit (Ping timeout: 264 seconds)
14:36:45  * node-ghjoined
14:36:45  * node-ghpart
15:05:00  * bnoordhuisjoined
16:08:35  * bnoordhuisquit (Ping timeout: 260 seconds)
16:16:05  * rmgjoined
17:14:51  * bnoordhuisjoined
17:19:59  * bnoordhuisquit (Ping timeout: 260 seconds)
17:25:00  * jgijoined
17:43:27  * bnoordhuisjoined
17:49:03  * node-ghjoined
17:49:03  * node-ghpart
18:06:36  * node-ghjoined
18:06:37  * node-ghpart
18:09:12  * jgiquit (Quit: jgi)
18:36:44  * jgijoined
19:06:22  * jgiquit (Quit: jgi)
19:43:54  <jbergstroem>orangemocha: rebooting is a pretty big task to handle is all. grepping for node owned by iojs and possibly some additional stuff would cover 99% of our issues right now
22:49:02  <jbergstroem>btw, confirmed with osuosl that they had network issues the other day.