00:03:47  <rvagg>consistent problems with xgene-2 and _one_ of the two jenkins slave processes running there just dying and not being restarted .. I've updated slave.jar but I'm not sure that's the problem, it's just weird that it's only that one host
00:07:16  <jbergstroem>crashes? memory issues/
00:08:08  <jbergstroem>rvagg: can i take remove smartos153 slave now? (have you done a successful release with smartos14)
00:35:19  * flybymejoined
00:38:38  * bnoordhuisquit (Ping timeout: 265 seconds)
00:41:41  <flybyme>I need to build most versions of node on armv7
00:41:52  <flybyme>I need the node binaries any advice?
00:44:54  <rvagg>jbergstroem: make it so
00:45:39  <rvagg>flybyme: armv7 binaries are available for node v4+ from nodejs.org, before that it's hit and miss, some of them are broken on arm, they are not tested or officially supported but should mostly work ..
00:47:18  <flybyme>what would be the best way to go back and build them for arm?
00:47:51  <flybyme>I know you guys use Jenkins but that seems for new release
00:47:58  <flybyme>I need to go back
00:48:10  <jbergstroem>ok, gone
00:50:36  <rvagg>flybyme: same was as you do for normal builds
00:50:59  <rvagg>flybyme: in earlier 0.10 it's dicey and you'll probably not have much luck, but beyond a certain point it was just supported by `configure` and `make`
00:51:14  <rvagg>flybyme: i.e. `./configure && make`
00:52:34  <flybyme>rvagg: Yeah thats kinda what im doing now. I have a script that is compiling them now
00:52:58  <flybyme>rvagg: you dont happen to know of a script of module that does this do you?
00:53:34  <rvagg>flybyme: not for all versions, probably something you'll want to code up in bash I suppose
00:53:52  <rvagg>flybyme: you can get version numbers from nodejs.org/dist/index.tab (or .json) if you need it
00:55:05  <rvagg>download source from nodejs.org, or clone the repo and check out each tag for that version number (before 0.10.41 and 0.12.9 the tags you want in git are `v0.y.z-release`, after that they are just `vx.y.z`, including v4+)
00:56:45  <flybyme>thanks for the link nodejs.org/dist/index.json
01:05:14  * node-ghjoined
01:05:14  * node-ghpart
01:12:37  * Fishrock123joined
01:53:03  * Fishrock123quit (Quit: Leaving...)
02:30:20  * jgiquit (Quit: jgi)
03:42:24  * trottjoined
04:23:51  * evanlucasjoined
04:24:11  * evanluca_quit (Read error: Connection reset by peer)
05:05:24  * jgijoined
05:07:02  * trottquit (Ping timeout: 255 seconds)
05:20:09  * jgiquit (Quit: jgi)
05:53:21  * evanlucasquit (Read error: Connection reset by peer)
05:54:00  * evanlucasjoined
05:56:58  * jgijoined
06:03:57  * trottjoined
06:08:06  * trottquit (Ping timeout: 240 seconds)
08:05:33  * trottjoined
08:09:35  * trottquit (Ping timeout: 240 seconds)
08:57:09  * evanlucasquit (Read error: Connection reset by peer)
08:57:49  * evanlucasjoined
09:53:13  * jgiquit (Quit: jgi)
10:06:57  * trottjoined
10:11:06  * trottquit (Ping timeout: 240 seconds)
10:34:18  * bnoordhuisjoined
12:08:24  * trottjoined
12:12:44  * trottquit (Ping timeout: 255 seconds)
12:45:32  * node-ghjoined
12:45:32  * node-ghpart
12:45:42  * node-ghjoined
12:45:42  * node-ghpart
13:15:17  * bnoordhuisquit (Ping timeout: 246 seconds)
13:47:31  * trottjoined
13:54:01  * trottquit (Quit: leaving)
14:21:35  * bnoordhuisjoined
14:25:59  * bnoordhuisquit (Ping timeout: 246 seconds)
14:56:06  * bnoordhuisjoined
15:26:05  * node-ghjoined
15:26:05  * node-ghpart
16:17:55  * Fishrock123joined
16:57:09  * jgijoined
17:01:15  * bnoordhuisquit (Ping timeout: 240 seconds)
17:01:16  * jgiquit (Client Quit)
17:27:23  * bnoordhuisjoined
17:29:56  * jgijoined
18:29:14  * jgiquit (Quit: jgi)
18:40:00  * jgijoined
18:48:00  <jbergstroem>jgi: there's probably a few vm's you can remove from our account at joyent
18:48:17  <jgi>jbergstroem: cool, which ones?
18:49:50  <jbergstroem>jgi: we know the old release bot isn't in use (jenkins-smartos-base-13.3.1), jenkins-centos-5.7 seems irrelevant, then there's a few older jenkins-* that at least aren't hooked up to the new ci. i'm happy to redeploy a few if we want some extra horse power
18:50:14  <jbergstroem>jgi: i haven't accessed most of them though, so please confirm
18:50:28  <jbergstroem>(ie, they might be connected to other stuff)
18:51:45  <jgi>jbergstroem: ok, if they’re not stopped, let’s stop them for a while, and then if nothing breaks, we’ll delete them
18:52:20  <jbergstroem>jgi: i'm pretty sure nothing will break in the "new" ci at least.
18:52:45  <jgi>jbergstroem: ok, the old CI has been stopped a few weeks ago, and is not used by anyone
18:53:39  <jbergstroem>jgi: cool. you probably know that list (of running vms, like freebsd-4core test) better than I do. The vm's with the new naming conventions on top are the only one's i've connected and are currently in use.
18:53:53  <jgi>jbergstroem: sounds good
18:55:09  <jgi>jbergstroem: where’s the website hosted now?
18:55:16  <jbergstroem>jgi: digitalocean
18:55:23  <jgi>ok
18:55:32  <jgi>jbergstroem: same for libuv?
18:55:55  <jbergstroem>jgi: i don't know anything about libuv hosting, sorry
18:56:24  <jbergstroem>jgi: probably off github or somehitng
18:56:42  <jgi>jbergstroem: yeah, that’s what nslookup tells me
18:56:55  <jgi>jbergstroem: I’ll check with saghul first before pulling the plug though
18:57:08  <jbergstroem>jgi: do it
18:57:57  <jgi>jbergstroem: I stopped all VMs except libuv-www and the ones you added that use the new naming convention
18:58:21  <jgi>jbergstroem: if anything breaks, let me know :)
18:58:32  <jbergstroem>jgi: cool. we'll get an alert in here if anything tied to the new ci goes down
18:59:23  <jbergstroem>jgi: there's unfortunately a bit of issues related to running network testing on vm's deployed on triton. my plan was to add a vm or two, but that needs further work if so. (broadcast and other networking stuff is different)
19:00:00  <jgi>jbergstroem: Interesting. What do you mean by “network testing"?
19:00:36  <jbergstroem>jgi: tests that use broadcast, loopback in our test suite
19:00:43  <jbergstroem>jgi: it's documented in triton
19:01:00  <jbergstroem>jgi: we had similar issues running tests in freebsd jails
19:13:43  <jgi>jbergstroem: ok that makes sense
20:33:54  <jbergstroem>I'm starting to doubt that enabled=yes for init scripts actually works. Need to confirm that
20:35:19  <jbergstroem>(ansible)
21:19:29  * jgiquit (Quit: jgi)
21:30:28  * jgijoined
21:38:31  * evanluca_joined
21:40:06  * evanlucasquit (Ping timeout: 240 seconds)
22:03:31  * jgiquit (Quit: jgi)
22:20:19  * jgijoined
22:37:55  * jgiquit (Quit: jgi)
22:44:11  * jgijoined
22:59:35  * node-ghjoined
22:59:36  * node-ghpart
23:22:25  * jgiquit (Quit: jgi)
23:32:52  * jgijoined