00:30:13  * jgijoined
00:55:18  * jgiquit (Quit: jgi)
00:56:55  * bnoordhuisquit (Ping timeout: 260 seconds)
00:57:44  * jgijoined
01:11:45  * jgiquit (Quit: jgi)
01:13:04  * Fishrock123quit (Quit: Leaving...)
01:30:17  * jgijoined
01:41:27  * jgiquit (Quit: jgi)
02:03:12  * bnoordhuisjoined
02:08:20  * bnoordhuisquit (Ping timeout: 256 seconds)
02:11:42  * jgijoined
02:12:15  * jgiquit (Client Quit)
02:14:56  * chorrelljoined
02:17:07  * jgijoined
02:24:05  * jgiquit (Quit: jgi)
03:07:54  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
03:09:47  * jgijoined
03:16:33  * jgiquit (Quit: jgi)
03:17:09  * jgijoined
03:33:30  * rmgjoined
03:34:06  * jgiquit (Quit: jgi)
03:34:46  * riznobjoined
03:38:05  * rmgquit (Ping timeout: 245 seconds)
04:16:56  * node-ghjoined
04:16:56  * node-ghpart
04:23:16  * jgijoined
04:26:45  * jgiquit (Client Quit)
04:27:13  * trottjoined
04:28:53  * jgijoined
04:30:33  * jgiquit (Client Quit)
04:31:39  * riznobquit (Ping timeout: 265 seconds)
04:35:49  * riznobjoined
04:48:34  * riznobquit (Ping timeout: 265 seconds)
04:58:15  * jbergstroemquit (Remote host closed the connection)
04:58:47  * jbergstroemjoined
05:26:23  * jgijoined
05:40:42  * jgiquit (Quit: jgi)
05:47:59  * jgijoined
05:56:35  * trottquit (Ping timeout: 264 seconds)
05:58:27  * trottjoined
05:59:36  * riznobjoined
06:01:25  * riznob_joined
06:04:27  * riznobquit (Ping timeout: 265 seconds)
06:11:12  <jbergstroem>jgi: is there something I can do to change the default ssh key when provisioning hosts at joyent?
06:12:15  <jgi>jbergstroem: what do you mean by default?
06:12:19  <jbergstroem>jgi: as-is, I get the one provided by you a while ago. Optimally, I'd like to be able to choose from the one's I add through my account.
06:12:35  <jbergstroem>jgi: or are they available through logging in as jbergstroem@ over ssh?
06:13:53  <jgi>jbergstroem: you need to be able to login as the user “NodeCore”
06:14:05  <jgi>jbergstroem: in Joyent’s portal
06:14:38  <jbergstroem>jgi: gotcha. not cool enough 8-)
06:15:31  <jgi>jbergstroem: no, it’s more due to a limitation of SmartLogin (the SSH auth plugin used to check for SSH keys in JPC user accounts when logging-in via ssh)
06:15:50  <jgi>jbergstroem: I’ll check back with the developers of the plugin to see if that has been fixed
06:15:58  <jbergstroem>jgi: thanks
06:16:04  <jbergstroem>jgi: btw i think its safe to start deleting old vm's
06:17:10  * node-ghjoined
06:17:11  * node-ghpart
06:21:35  <jgi>jbergstroem: sounds good. I’ll see what I can do to give you full autonomy to manage the resources provided by Joyent and used by the foundation, without having to ask me e.g to change ssh keys.
06:22:15  <jbergstroem>jgi: that'd be great. if possible, a shared account (limited to people in the infra group) would be preferrable since we share secrets by gpg keys.
06:22:46  <jbergstroem>jgi: i know it doesn't play great with audits etc, but its a pretty nice way for the build group to handle access
06:23:13  <jgi>jbergstroem: yes, the problem is that until recently, shared accounts didn’t work for SmartLogin and ssh keys added to sub-users. So I’m not sure we’ll be able to use that.
06:23:32  <jbergstroem>jgi: ok. let me know how it goes
06:23:48  <jgi>jbergstroem: sharing the password for one single account will be the last resort solution.
06:23:59  <jgi>jbergstroem: I’ll keep you updated.
06:35:46  * riznobjoined
06:39:15  * riznob_quit (Ping timeout: 265 seconds)
06:48:34  * jgiquit (Quit: jgi)
07:12:56  <jbergstroem>^ restarted jenkins
07:12:56  * trottquit (Quit: leaving)
07:13:05  <jbergstroem>does anyone have a clue as to what happens here? https://ci.nodejs.org/job/node-test-binary-windows/473/RUN_SUBSET=1,VS_VERSION=vs2013,label=win2008r2/console
07:29:16  * bnoordhuisjoined
07:35:07  * rmgjoined
07:40:07  * rmgquit (Ping timeout: 260 seconds)
08:08:35  * bnoordhuisquit (Ping timeout: 264 seconds)
08:09:15  * bnoordhuisjoined
08:24:45  * riznobquit
09:18:50  * bnoordhuisquit (Ping timeout: 272 seconds)
09:21:15  * bnoordhuisjoined
09:35:46  * rmgjoined
09:40:14  * rmgquit (Ping timeout: 246 seconds)
09:57:30  * imjacobclarkjoined
11:07:26  * imjacobclarkquit (Ping timeout: 240 seconds)
11:09:44  * evanluca_joined
11:10:30  * evanlucasquit (Read error: Connection reset by peer)
11:23:44  * evanluca_quit (Read error: Connection reset by peer)
11:25:06  * evanlucasjoined
11:55:09  * evanlucasquit (Read error: Connection reset by peer)
11:55:38  * evanlucasjoined
12:13:43  * bnoordhuisquit (Ping timeout: 265 seconds)
12:35:48  <joaocgreis>happened again, different machine: https://ci.nodejs.org/job/node-test-binary-windows/474/RUN_SUBSET=1,VS_VERSION=vs2013,label=win2008r2/console
12:35:53  <joaocgreis>restarted both
13:19:40  * bnoordhuisjoined
13:24:18  * bnoordhuisquit (Ping timeout: 255 seconds)
13:37:32  * rmgjoined
13:37:46  * node-ghjoined
13:37:47  * node-ghpart
13:40:04  * node-ghjoined
13:40:04  * node-ghpart
13:41:51  * rmgquit (Ping timeout: 255 seconds)
13:51:00  * bnoordhuisjoined
13:51:41  <orangemocha>joaocgreis, maybe a dangling node instance?
13:53:25  <orangemocha>Is it possible to have a process list diagnostic output before that command?
14:10:34  * bnoordhuisquit (Ping timeout: 245 seconds)
14:23:43  * chorrelljoined
14:37:39  <joaocgreis>orangemocha:
14:37:55  <joaocgreis>I checked the diagnostic output, no node was running
14:40:37  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
15:02:38  * bnoordhuisjoined
15:04:41  * evanluca_joined
15:05:38  * evanlucasquit (Read error: Connection reset by peer)
15:12:19  * node-ghjoined
15:12:19  * node-ghpart
15:14:34  * node-ghjoined
15:14:34  * node-ghpart
15:15:37  * Fishrock123joined
15:37:41  * bnoordhuisquit (Ping timeout: 265 seconds)
15:38:06  * rmgjoined
15:42:47  * rmgquit (Ping timeout: 264 seconds)
16:12:08  * chorrelljoined
16:14:49  * bnoordhuisjoined
16:38:01  * jgijoined
16:43:23  * bnoordhuisquit (Ping timeout: 246 seconds)
16:56:37  * bnoordhuisjoined
17:17:33  * jgiquit (Quit: jgi)
17:17:57  * jgijoined
17:18:56  * rmgjoined
17:22:14  * jgiquit (Ping timeout: 246 seconds)
17:28:40  * node-ghjoined
17:28:41  * node-ghpart
17:52:14  * jgijoined
17:53:01  * riznobjoined
17:57:16  * riznob_joined
17:59:22  * imjacobclarkjoined
17:59:47  * riznobquit (Ping timeout: 265 seconds)
18:04:23  * imjacobclarkquit (Remote host closed the connection)
18:04:49  * imjacobclarkjoined
18:05:02  * riznobjoined
18:08:29  * riznob_quit (Ping timeout: 265 seconds)
18:09:08  * imjacobclarkquit (Ping timeout: 246 seconds)
18:11:28  * riznobquit
18:24:06  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
19:10:19  * evanluca_changed nick to evanlucas
19:21:49  * thealphanerdquit (Quit: farewell for now)
19:32:48  <jbergstroem>joaocgreis: got a clue as to whats up?
19:32:57  <jbergstroem>(re the git issue)
19:35:10  * chorrelljoined
19:35:24  * thealphanerdjoined
19:47:59  * jgiquit (Quit: jgi)
19:49:52  * jgijoined
20:00:58  <jgi>jbergstroem: checked again if ssh keys added to sub-users account on JPC was supported and it’s still not supported. After some discussions with other JPC developers, the best way to have several people be able to manage resources on JPC is to share the account’s login/password.
20:01:32  <jgi>jbergstroem: I’m OK with that.
20:30:30  <jbergstroem>jgi: roger. if you can pass me the details i will update the password and add it to the infra secrets.
20:30:46  <jgi>jbergstroem: sounds good
20:31:33  <jbergstroem>jgi: feel free to spring clean the old vm's as well; i havent created any of them so i don't know if somehting needs to be around
20:32:31  <jgi>jbergstroem: I’ll start deleting the ones that don’t have any data that we might want to backup
20:32:40  <jbergstroem>jgi: yep
21:16:42  * jgiquit (Quit: jgi)
21:24:16  * jgijoined
21:33:40  <michael___>jbergstroem looks like once you remove the ppc release machine it was not possible to recreate
21:33:56  <michael___>the summary of the resources looks wrong as it still includes the machine which was removed
21:34:00  <jbergstroem>michael___: its been dragging along for weeks :( first there was a bug in removing it, so i had to wait for it to be manually removed
21:34:10  <michael___>I sent another email to support
21:34:13  <jbergstroem>michael___: then it was a bug with resources not being recalculated cause someone deleted it manually
21:34:19  <jbergstroem>michael___: i've pinged them a few times; waiting to hear back
21:34:29  <michael___>ah ok, I just sent additional email
21:34:31  <michael___>emails
21:34:33  <jbergstroem>good :)
21:35:17  <michael___>I'm also trying to ping people in the #osuosl channel but email is the officially supported way to contact them
21:35:40  <michael___>Catching up on email I see there were some problems one of the days I was away but that it resolved itself
21:37:31  <michael___>Anything else on the build front I need to catch up on ?
21:38:34  <jbergstroem>michael___: unless you want to hear about rain in Sydney, not so much.
21:38:36  <michael___>I'm guessing the slow response on the osuosl side might be the Christmas holidays particularly since its at a University where students are away for a longer period
21:38:52  <michael___>At this point I'd take rain over snow and -17
21:39:12  <jbergstroem>michael___: there were issues with osuosl bots but I confirmed through support that they had issues with other machines saturating their internet
21:39:20  <jbergstroem>michael___: theres a closed issue in the build repo about it
21:39:35  <michael___>good to know the issue was understood
21:46:01  * jgiquit (Quit: jgi)
22:24:40  * trottjoined
22:27:39  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:38:45  <jbergstroem>if this smartos slowness keeps going i'm goign to have to redeploy to larger vm's :(
22:40:34  * jgijoined
23:02:05  * trott1joined
23:02:26  * trottquit (Ping timeout: 246 seconds)
23:19:22  * bnoordhuisquit (Ping timeout: 256 seconds)
23:25:32  <michael___>jbergstroem looks like they have it fixed up on osuol
23:25:44  <jbergstroem>michael___: yep; just got the email.
23:25:45  <michael___>I just manged to create a medium instance (4G ram, 2 CPU)
23:26:22  <michael___>So if you think we only need 2 cpu/4G for the release machines
23:26:22  <jbergstroem>michael___: yeah i'll create two new release machines then redeploy the test ones
23:26:35  <jbergstroem>we only need 2/2 tbh
23:26:42  <jbergstroem>thats what we have on most of the other stuff at the moment
23:27:04  <michael___>k, if you can please only do one of the test machines on a give platform at a time so we always have one working for builds
23:27:25  <jbergstroem>of course
23:27:26  <michael___>The other FYI is that I had to log into the machines and set up the root user so that the existing playlists would work
23:27:39  <jbergstroem>yeah thats still a bit quirky
23:27:45  <jbergstroem>i've added our new pubkeys so it should be eaiser
23:28:05  <jbergstroem>i usually step our current ones and skip everything releated to pubkeys
23:28:08  <michael___>I think the user on ubuntu is ubuntu and on fedora its fedora
23:28:38  <michael___>I also had to change the default ssh config for the user so that it would allow the root user to log in
23:29:02  <michael___>it seems to have a redirect installed that just said "don't use root"
23:29:20  <michael___>I think other than that is was just running the ansible script
23:29:27  <michael___>let me know if you run into any other issues
23:29:34  <jbergstroem>that's fine. we'll sudo up if possible
23:29:39  <jbergstroem>i'll be good, thanks :)
23:30:00  <michael___>sudo would be even better
23:30:34  <jbergstroem>im trying to write some kind of logic for that in the refactor
23:30:40  <jbergstroem>its going.. "ok"
23:31:20  <michael___>The change to NODE_PIPE_DIR did cause me more hassle than I thought as some of our builds are on nfs and one of the tests did not like a cross link to /tmp
23:31:56  <michael___>and jenkins does not give me a good way to get a directory other than the workspace which is what was too deep resulting in problems
23:32:32  <michael___>I have a work around but its a hack for now
23:33:28  <thealphanerd>i just botched test commit osx
23:33:29  <thealphanerd>https://ci.nodejs.org/job/node-test-commit-osx/
23:33:42  <thealphanerd>sorry... was working on a fork of it and lost track of windows
23:33:47  <thealphanerd>how do you roll back a change?
23:33:54  <thealphanerd>jbergstroem ^^
23:34:47  <jbergstroem>thealphanerd: you mean you edited a configuration?
23:34:52  <thealphanerd>indeed
23:34:54  <thealphanerd>I'm very sorry
23:35:03  <jbergstroem>thealphanerd: we do nightly backups. let me chase that up
23:35:12  <thealphanerd>thanks
23:35:19  <jbergstroem>thealphanerd: but in short; no good routine. everything is considered live.
23:35:38  <jbergstroem>thealphanerd: ify ou need to tinker around, copy thej ob
23:35:56  <thealphanerd>it's what I thought I was doing.. will be more careful in the future
23:37:06  <thealphanerd>jbergstroem could we add this plugin to avoid something like this in the future? --> https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
23:37:33  <jbergstroem>thealphanerd: to be honest, the less plugins the better :(
23:37:38  <thealphanerd>fair enough
23:37:49  <jbergstroem>create an issue about it though
23:40:38  * node-ghjoined
23:40:39  * node-ghpart
23:41:11  <thealphanerd>jbergstroem luckily enough I think the changes I made are actually non breaking atm... phew. thanks for the help with this
23:43:22  * node-ghjoined
23:43:22  * node-ghpart
23:43:23  <jbergstroem>thealphanerd: thanks for creating the issue
23:43:43  <jbergstroem>lel that engrish
23:44:37  * node-ghjoined
23:44:37  * node-ghpart
23:45:30  <thealphanerd>jbergstroem I think I managed to revert it by memory
23:45:42  <thealphanerd>https://ci.nodejs.org/job/node-test-commit-osx/1658/console
23:46:21  <jbergstroem>thealphanerd: i'm logging in to the backup stuff now
23:46:26  <thealphanerd>make that https://ci.nodejs.org/job/node-test-commit-osx/1659/console
23:46:29  <jbergstroem>thealphanerd: i'll try to find the old job and make a diff just to make sure
23:46:45  <thealphanerd>appreciate it :D (I'm just trying to make sure we have no down time)