02:34:19  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
03:34:55  * not-an-aardvarkjoined
05:21:43  * sxaquit (Ping timeout: 245 seconds)
05:23:05  * sxajoined
06:39:47  * thealphanerdchanged nick to mylesborins
08:03:12  <mylesborins>jbergstroem oh hai you around?
08:05:04  <mylesborins>trying to figure out the ips to certain smartos machines so I can ensure there are no phantom processes running
09:04:19  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
09:05:20  <phillipj>mylesborins: not listed here? https://github.com/nodejs/build/blob/master/setup/smartos/README.md
09:05:34  <mylesborins>only lists 14 not 15
11:25:07  * mylesborinsquit (Quit: farewell for now)
11:25:37  * thealphanerdjoined
11:27:07  * node-ghjoined
11:27:07  * node-ghpart
11:31:01  * node-ghjoined
11:31:01  * node-ghpart
11:36:20  * node-ghjoined
11:36:20  * node-ghpart
11:36:54  <jbergstroem>thealphanerd: this is probably more up to date: https://github.com/jbergstroem/build/blob/feature/refactor-the-world/ansible/inventory.yml
11:37:15  <jbergstroem>thealphanerd: but; if you want the ip's you can get them from jenkins as well! just check the host through ci.nodejs.org/computer/
11:37:39  <jbergstroem>thealphanerd: also, there's a inventory.yml -> ssh config playbook in that repo
11:45:00  * node-ghjoined
11:45:00  * node-ghpart
11:48:05  * node-ghjoined
11:48:05  * node-ghpart
12:19:25  * jbergstroemquit (*.net *.split)
12:19:34  * jbergstroemjoined
12:38:44  <jbergstroem>thealphanerd: ..or try something like ansible -m shell -a 'ps auxwww | grep "iojs" | grep -v java' "*smartos*"
14:05:33  * node-ghjoined
14:05:33  * node-ghpart
14:07:34  * node-ghjoined
14:07:34  * node-ghpart
14:21:39  * node-ghjoined
14:21:39  * node-ghpart
14:34:18  * node-ghjoined
14:34:18  * node-ghpart
14:34:34  * node-ghjoined
14:34:34  * node-ghpart
14:57:53  * chorrelljoined
15:48:27  * gibfahnjoined
15:48:37  * gibfahnquit (Client Quit)
15:48:57  * gibfahnjoined
16:45:14  * wyattjoined
17:29:16  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
17:32:54  * node-ghjoined
17:32:54  * node-ghpart
17:34:54  * node-ghjoined
17:34:54  * node-ghpart
17:53:39  * node-ghjoined
17:53:39  * node-ghpart
17:53:49  * node-ghjoined
17:53:49  * node-ghpart
18:06:15  * gibfahnquit (Ping timeout: 260 seconds)
18:57:16  * chorrelljoined
18:59:07  * wyattquit (Remote host closed the connection)
19:01:19  * wyattjoined
19:11:33  * wyattquit (Remote host closed the connection)
19:12:54  * wyattjoined
19:23:09  * wyattquit (Remote host closed the connection)
19:28:34  * wyattjoined
19:35:46  * Trottquit (*.net *.split)
19:35:46  * italoacasasquit (*.net *.split)
19:35:46  * ofrobotsquit (*.net *.split)
19:35:46  * phillipjquit (*.net *.split)
19:35:47  * ljharbquit (*.net *.split)
19:38:49  * wyattquit (Remote host closed the connection)
19:41:09  * wyattjoined
19:41:33  * ljharbjoined
19:43:44  * italoacasasjoined
19:44:06  * phillipjjoined
19:46:08  * ofrobotsjoined
19:47:23  * Trottjoined
19:49:06  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
20:01:47  * thefourtheyejoined
20:04:38  <thefourtheye>The failures from https://github.com/nodejs/node/pull/10456 are affecting all other CI runs. I am afraid there are few node.js processes running on those machines which hold on to specific ports.
20:04:52  <thefourtheye>How can we fix this?
20:09:00  * node-ghjoined
20:09:00  * node-ghpart
20:38:51  * node-ghjoined
20:38:51  * node-ghpart
20:43:27  <jbergstroem>thefourtheye: we don't have an automated way of killing processes after each run. we can log in and reap processes but the encouraged way would probably be giving temporary access to them so you/someone can figure out whats going on?
20:43:35  <jbergstroem>as in, try to sort it out
21:02:16  <wyatt>is there a call?
21:02:29  * node-ghjoined
21:02:29  * node-ghpart
21:08:37  <jbergstroem>wyatt: Next meeting: January 10, 2017 - https://docs.google.com/document/d/1-joUlwaNYirwDlG9sFUyrHKa43ljgRPpj5o-Ygv9JRc/edit
21:12:06  <wyatt>thanks
21:28:54  <jbergstroem>np's
21:29:05  <jbergstroem>had time to look at the sunos->smartos stuff?
21:33:19  * node-ghjoined
21:33:19  * node-ghpart
21:35:57  * node-ghjoined
21:35:57  * node-ghpart
21:45:49  * node-ghjoined
21:45:49  * node-ghpart
21:53:12  * node-ghjoined
21:53:12  * node-ghpart
21:54:49  * node-ghjoined
21:54:49  * node-ghpart
22:08:44  <wyatt>jbergstroem yes, it appears that allocating 8gb of memory on that machine takes around 15s... this is why https://github.com/nodejs/node/blob/master/test/sequential/test-buffer-creation-regression.js can timeout... plus it allocates 8gb of memory
22:35:26  * node-ghjoined
22:35:27  * node-ghpart
22:49:20  * node-ghjoined
22:49:20  * node-ghpart
23:00:49  * lanceballchanged nick to lance|afk