02:34:53  * williamkapke_joined
02:41:57  * williamkapkequit (*.net *.split)
02:42:33  * williamkapke_changed nick to williamkapke
06:37:17  * mscdexjoined
06:38:56  <mscdex>it looks like one of the VS2015 workers (test-rackspace-win2012r2-x64-3) is having memory exhaustion issues?: https://ci.nodejs.org/job/node-compile-windows/6479/label=win-vs2015/console
10:08:11  <jbergstroem>joaocgreis: ^ should i reboot?
11:25:09  * mylesborinsquit (Quit: farewell for now)
11:25:40  * mylesborinsjoined
12:10:49  * jenkins-monitorquit (Remote host closed the connection)
12:11:00  * jenkins-monitorjoined
12:42:15  * node-ghjoined
12:42:16  * node-ghpart
13:35:42  * jenkins-monitorquit (Remote host closed the connection)
13:35:50  * jenkins-monitorjoined
15:33:48  * sgimenojoined
16:18:08  * mscdexpart ("Leaving")
16:25:08  <joaocgreis>jbergstroem: please reboot, thanks
16:30:25  <jbergstroem>joaocgreis: done
16:41:17  <sgimeno>hi, is there info available on the alpine34 bots in the CI? I've been trying to reproduce locally errors when running the libuv tests, but they run correctly on my environment
16:45:45  <jbergstroem>sgimeno: https://github.com/nodejs/build/pull/437
16:49:44  <sgimeno>jbergstroem, thanks! looking into it
17:10:12  <sgimeno>jbergstroem, is this exactly what runs the libuv tests? There's some dependencies missing in the Dockerfile: libtool automake autoconf...
17:10:20  <jbergstroem>ah libuv
17:10:33  <jbergstroem>libuv runs on the other machines; not in docker
17:10:36  <jbergstroem>here:
17:10:56  <jbergstroem>https://github.com/jbergstroem/build/tree/feature/refactor-the-world/ansible
17:11:45  <jbergstroem>sgimeno: check this file, specifically line as well as above: https://github.com/jbergstroem/build/blob/feature/refactor-the-world/ansible/roles/baselayout/vars/main.yml#L31
17:14:04  <sgimeno>jbergstroem, so they are not running on docker, right?
17:14:19  <jbergstroem>no; they are running on smartos's linux emulation layer
17:14:21  <jbergstroem>"almost kvm"
17:14:29  <jbergstroem>at joyent
17:14:40  <sgimeno>so, there's no simple way to reproduce the environment
17:14:52  <jbergstroem>docker should work pretty well though
17:15:02  <jbergstroem>i reckon you should get the same errors through a docker env with said pacakges
17:15:11  <sgimeno>yeah works great, but all the tests passes with docker
17:15:23  <sgimeno>but there are some tests that always fail on the bot
17:16:25  <sgimeno>I mean, on docker all the tests pass consistently
17:16:35  <sgimeno>not on the CI bot
17:20:09  <jbergstroem>oh
17:20:11  <jbergstroem>let me check
17:20:58  <jbergstroem>sgimeno: we can probably give you access to a machine
17:21:41  <sgimeno>that would be nice
17:23:31  * node-ghjoined
17:23:32  * node-ghpart
17:24:46  <sgimeno>jbergstroem, thanks! btw I'm @santigimeno @ github
17:24:56  <jbergstroem>sorry you're right
17:24:57  <jbergstroem>:]
17:25:19  * node-ghjoined
17:25:19  * node-ghpart
17:42:30  * node-ghjoined
17:42:30  * node-ghpart
17:45:45  * node-ghjoined
17:45:45  * node-ghpart
19:05:42  * jenkins-monitorquit (Remote host closed the connection)
19:05:51  * jenkins-monitorjoined
21:25:42  * jenkins-monitorquit (Remote host closed the connection)
21:25:50  * jenkins-monitorjoined