19:22:04  <mhdawson>will do
19:24:21  * node-ghjoined
19:24:21  * node-ghpart
19:25:06  * node-ghjoined
19:25:06  * node-ghpart
19:32:49  * node-ghjoined
19:32:49  * node-ghpart
19:35:18  * node-ghjoined
19:35:19  * node-ghpart
19:42:05  <jbergstroem>can somemone tell me if the links work?
20:01:55  * lance|afkchanged nick to lanceball
20:05:24  * node-ghjoined
20:05:24  * node-ghpart
20:19:02  <jbergstroem>My internet just died
20:19:24  <jbergstroem>Trying to get back through 3g. Michael, can you host?
20:20:10  * node-ghjoined
20:20:10  * node-ghpart
20:20:40  * node-ghjoined
20:20:40  * node-ghpart
20:21:10  * node-ghjoined
20:21:10  * node-ghpart
20:21:21  <thealphanerd>jbergstroem :(
20:21:22  <thealphanerd>moving forward w/o you :D
20:22:01  * node-ghjoined
20:22:01  * node-ghpart
20:26:27  * gibfahnjoined
20:32:24  * node-ghjoined
20:32:24  * node-ghpart
20:58:21  * node-ghjoined
20:58:21  * node-ghpart
20:58:46  * node-ghjoined
20:58:46  * node-ghpart
20:59:31  * gibfahnquit (Ping timeout: 260 seconds)
21:03:09  * node-ghjoined
21:03:10  * node-ghpart
21:30:22  <joaocgreis>jbergstroem: re https://github.com/jbergstroem/build/blob/feature/refactor-the-world/ansible/inventory.yml , can you use the DNS name for the Azure hosts instead? They might change the IP if they go down. Not a big issue if you can't, they have NEVER went down :)
21:30:38  <jbergstroem>joaocgreis: sure
21:31:20  <jbergstroem>joaocgreis: if you name them 1:1 i can write a script that reuses inventory_hostname to ansible_hostname
21:32:09  <jbergstroem>joaocgreis: is that a flag btw? i've never had my azure hosts change ip
21:34:17  * evanlucasjoined
21:34:40  <joaocgreis>jbergstroem: there's a dns name lenght limit, so I removed part of the name: https://github.com/nodejs/build/blob/master/setup/ansible-inventory#L155-L165
21:35:23  <jbergstroem>ok so we can't then
21:35:35  <jbergstroem>i guess we can script that once we can create hosts through the inventory jobs
21:35:44  <joaocgreis>jbergstroem: the IP is allocated to the cloud service, not the VM, so the cloud service has to go down for the IP to change and that's not easy it seems.
21:35:56  <jbergstroem>joaocgreis: ah, probs why i haven't seen it either
21:36:07  <jbergstroem>been doing a lot of testing on azure lately
21:36:54  <joaocgreis>sometimes the windows machines on rackspace shutdown and I have to log in to the rackspace portal to bring them back, but that has never ever happened in Azure
21:38:27  <jbergstroem>dgram is pretty consistently stalling at freebsd hosts: https://gist.github.com/jbergstroem/0eb82bb0eefa3f7620a395aca583d4e1
21:39:27  <jbergstroem>sorry, old paste
21:39:31  <jbergstroem>but yeah. dgram :'(
21:42:37  <jbergstroem>ok, run on latest master; no trailing processes or known issues on any init script: https://ci.nodejs.org/job/node-test-commit-freebsd/4766/
21:44:32  <jbergstroem>fbsd11/clang 3.8 seems faster than fbsd10/3.4
21:50:16  <jbergstroem>on freebsd11 parallel/test-npm-install looks reproducable
21:50:52  <jbergstroem>on 10, 3 timeouts so far
21:51:24  <jbergstroem>i wonder how many failures the stalling dgram child is related to
21:51:33  * node-ghjoined
21:51:33  * node-ghpart
21:52:24  * node-ghjoined
21:52:25  * node-ghpart
21:52:53  * node-ghjoined
21:52:53  * node-ghpart
21:53:04  * node-ghjoined
21:53:05  * node-ghpart
22:02:43  * node-ghjoined
22:02:43  * node-ghpart
22:06:23  * node-ghjoined
22:06:23  * node-ghpart
22:18:43  * node-ghjoined
22:18:43  * node-ghpart
22:28:43  <jbergstroem>great. first green build and ci gives up
22:28:51  <jbergstroem>so tired of this :[
23:07:49  <Trott>Would the Build WG be the right place to have ljharb at a meeting so we can sort out how to set things up in the download directory for maximum nvm happiness? /cc thealphanerd There's some chatter between ljharb and me above about this, but I'd really like to see us get it right once-and-for-all if at all possible. But I'm not sure the Build WG is the place
23:07:49  <Trott>for it. Is it? (Also not sure ljharb wants to come to a meeting, but one thing at a time.)
23:07:59  <thealphanerd>\\
23:08:08  <thealphanerd>jbergstroem smart os and free bsd were acting super weird for me
23:08:32  <thealphanerd>I feel like build is the right place
23:08:38  <jbergstroem>Trott: its something in the middle of build/release teams
23:08:42  <thealphanerd>we can figure out the requirements and put a plan together
23:08:52  <jbergstroem>but its also jenkins crew seeing how the dropdowns in ci-release needs to be synced
23:09:25  <Trott>Maybe I can open an issue to at least get in writing my concerns and others can tack on from there.
23:13:04  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
23:14:45  * node-ghjoined
23:14:45  * node-ghpart
23:15:23  <jbergstroem>do itt
23:17:53  * node-ghjoined
23:17:53  * node-ghpart
23:20:40  <jbergstroem>can anyone else lgtm?
23:20:47  <jbergstroem>https://github.com/nodejs/build/issues/511
23:25:31  <ljharb>Trott: i'll come to any meetings i can make
23:25:35  <ljharb>* and am invited to
23:26:23  <jbergstroem>ljharb: cool
23:28:50  * node-ghjoined
23:28:50  * node-ghpart
23:28:55  <Trott>OK, opened an issue: https://github.com/nodejs/build/issues/515
23:29:33  <Trott>ljharb: Our Build WG meetings seem to be Tuesdays at 1PM Pacific Daylight Time.
23:30:29  * node-ghjoined
23:30:29  * node-ghpart
23:31:14  * node-ghjoined
23:31:14  * node-ghpart
23:36:24  * node-ghjoined
23:36:24  * node-ghpart
23:39:53  * node-ghjoined
23:39:53  * node-ghpart
23:41:26  * node-ghjoined
23:41:26  * node-ghpart
23:42:46  * node-ghjoined
23:42:46  * node-ghpart
23:54:02  * jbergstroemquit (Excess Flood)
23:54:18  * jbergstroemjoined