00:44:39  <jbergstroem>:-D
00:44:50  <jbergstroem>i'll restart
00:52:13  <jbergstroem>..or not; stuff in line
01:03:41  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
01:18:45  * ofrobotsjoined
01:22:20  * jgiquit (Quit: jgi)
02:09:35  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
02:13:45  * ofrobotsjoined
02:21:49  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
02:24:57  * ofrobotsjoined
02:25:09  * node-ghjoined
02:25:09  * node-ghpart
02:31:26  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
02:51:56  * evanluca_joined
02:52:25  * evanlucasquit (Read error: Connection reset by peer)
03:03:21  * ofrobotsjoined
03:13:06  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
03:50:25  * node-ghjoined
03:50:26  * node-ghpart
04:04:08  * evanluca_quit (Read error: Connection reset by peer)
04:04:40  * evanlucasjoined
04:22:42  * node-ghjoined
04:22:42  * node-ghpart
04:31:50  * rmgquit (Remote host closed the connection)
05:01:38  * evanlucasquit (Read error: Connection reset by peer)
05:02:40  * evanlucasjoined
05:17:06  * evanlucasquit (Read error: Connection reset by peer)
05:17:12  * evanluca_joined
06:01:18  <rvagg>curses to this new shared infra ssh key business!
06:12:34  * node-ghjoined
06:12:35  * node-ghpart
06:13:18  * node-ghjoined
06:13:18  * node-ghpart
08:02:34  * evanluca_quit (Read error: Connection reset by peer)
08:04:21  * evanlucasjoined
08:06:03  * evanlucasquit (Read error: Connection reset by peer)
08:06:36  * evanlucasjoined
10:19:51  * imjacobclarkjoined
10:32:36  * node-ghjoined
10:32:36  * node-ghpart
10:35:43  * node-ghjoined
10:35:44  * node-ghpart
10:39:08  * node-ghjoined
10:39:09  * node-ghpart
10:45:58  * evanlucasquit (Read error: Connection reset by peer)
10:46:42  * evanlucasjoined
11:08:23  <rvagg>orangemocha, jbergstroem, joaocgreis: as much as I'd love to chat with you fellas, we don't have a meeting planned as far as I can see and I don't really want to get up early for one cause I'm drowning in my backlog an am trying really hard to catch up, another early meeting is going to make things worse for me
11:10:25  * rmgjoined
11:12:49  <jbergstroem>rvagg: how about we stick to communication through pr's/issues then?
11:15:10  * rmgquit (Ping timeout: 260 seconds)
11:22:50  * evanlucasquit (Read error: Connection reset by peer)
11:23:55  * evanlucasjoined
12:44:15  * imjacobclarkquit (Ping timeout: 265 seconds)
13:11:08  * rmgjoined
13:15:56  * rmgquit (Ping timeout: 240 seconds)
13:58:52  * ofrobotsjoined
14:26:17  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
14:50:07  * ofrobotsjoined
15:37:05  * Fishrock123joined
15:45:37  <joaocgreis>rvagg: I don't think we have a meeting scheduled for today. I'm perfectly fine with discussing things less formally here and using github for commitment (and our meeting time is quite bad for me, can only make it when really needed)
15:51:05  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
16:08:16  * ofrobotsjoined
16:09:02  * ofrobotsquit (Client Quit)
16:27:55  * rmgjoined
16:43:59  <joaocgreis>jbergstroem: I logged in to ci, ps aux shows `-Dhudson.slaves.ChannelPinger.pingInterval=5`
16:44:12  <joaocgreis>that number is in minutes :s
16:44:26  <joaocgreis>that is causing the timeouts
16:45:02  <joaocgreis>does setting it to 2 cause problems in other non-azure slaves?
16:45:13  <joaocgreis>(btw, where do you set it?)
16:46:15  <joaocgreis>I looked for a way to change the timeout setting in Azure, but no luck so far
16:53:10  <joaocgreis>according to https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread , there's also a ping from the client. I'll try to set it in the slaves
17:00:55  * ofrobotsjoined
17:26:45  * saperquit (Read error: Connection reset by peer)
17:26:53  * saperjoined
17:39:13  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
18:06:18  <joaocgreis>test-rackspace-win2008r2-x64-2 is down because of me, working on it
18:40:43  <starefossen>working on scoring in jenkins monitor
18:42:46  * jgijoined
19:01:32  * ofrobotsjoined
19:08:50  * ofrobotsquit (Ping timeout: 260 seconds)
19:09:55  * ofrobotsjoined
19:10:25  * ofrobotsquit (Client Quit)
19:12:16  * ofrobotsjoined
19:26:04  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
19:37:07  <jbergstroem>joaocgreis: no, its seconds afaik
19:37:42  * jgiquit (Quit: jgi)
19:38:32  * jgijoined
19:38:47  <jbergstroem>ahh shit
19:39:06  <jbergstroem>hudson.remoting.Launcher.pingIntervalSec
19:39:51  <jbergstroem>joaocgreis: default is 5
19:42:24  <joaocgreis>jbergstroem: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/ChannelPinger.java#L108 , I might be missing something though
19:42:54  <joaocgreis>interval in that -D is minutes, but the interval for the slave is seconds (jenkins!!!)
19:43:26  * ofrobotsjoined
19:44:00  <joaocgreis>I'm launching the windows slaves with -Dhudson.remoting.Launcher.pingIntervalSec=60 and it has not crashed for 1h.. let's see how it holds
19:45:30  <jbergstroem>https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
19:49:14  <joaocgreis>from https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread I understand that hudson.slaves.ChannelPinger.pingInterval should be set on the master and hudson.remoting.Launcher.pingIntervalSec on the slaves
19:51:02  <joaocgreis>it may make sense that everything needs to be set on the master if slaves are launched by ssh
19:56:04  * ofrobotsquit (Quit: My Mac has gone to sleep. ZZZzzz…)
20:17:34  <jbergstroem>so, do I lower it?
20:17:58  <jbergstroem>as you see in that list there seems to be second granularity if we want
20:21:36  <starefossen>I am working on the downtime scoring
20:26:35  <jbergstroem>sweet
20:29:36  <starefossen>Sorry for the spam.
20:30:46  <joaocgreis>jbergstroem: I remember you said the best value is 5, what issues did you see with 2? Does that break other slaves?
20:31:19  <jbergstroem>joaocgreis: we can try again but i recall it being more offline/offline toggles
20:31:53  * node-ghjoined
20:31:53  * node-ghpart
20:32:59  <jbergstroem>joaocgreis: let me know if i should restart with it
20:34:26  <joaocgreis>the timeout of the azure load balancer is 4 minutes. Perhaps try with 3?
20:35:02  <joaocgreis>I changed the windows slaves, we can wait for a day or two to see if that solves anything
20:35:18  <jbergstroem>ok
20:36:43  <joaocgreis>where exactly do you change that setting in the ci server? It's usually easy to find jenkins idle during your night, I can try it tomorrow and restart
20:53:39  <joaocgreis>jbergstroem: ^
20:53:58  <jbergstroem>in /etc/default/jenkins
20:54:05  <jbergstroem>i've done hte change
20:54:15  <joaocgreis>thanks!
20:54:23  <jbergstroem>just go `service jenkins restart` next time you see it idle and let me know here
20:54:25  <jbergstroem>i'll do the same
20:55:35  <joaocgreis>also, I've changed jenkins.bat to download slave.jar when restarts happen. Found the recommendation in a jenkins page somewhere, seemed smart, so now windows auto-updates slave.jar
21:14:45  <jbergstroem>:/
21:21:33  <joaocgreis>I tried smaller servers in the rackspace account. Before, the huge 32core server took 9m37s to compile (vs2013). I tried general purpose 4core/4gb ram and it took 19m11s, I think that is too much. The 8core/8gb takes 12m32s, that seems good
21:22:11  <joaocgreis>so I plan to replace the huge servers by more 8core/8gb servers
21:23:07  <joaocgreis>jbergstroem: does that sound good to you?
21:23:26  <jbergstroem>sounds good
21:34:17  * Fishrock123quit (Quit: Leaving...)
22:40:00  <rvagg>nice work folks!
22:44:25  <jbergstroem>yay nginx security release
23:36:18  <jbergstroem>the jobs on ci seems to just stall
23:36:22  <jbergstroem>going to cancel and restart jenkins master
23:37:10  <jbergstroem>ok, after hte release job finishes
23:53:01  <jbergstroem>running a full backup of jenkins now, then i'll have a look at the build history plugin
23:59:09  <jbergstroem>gotta make sure ci is running smoothly for the jan 28 releases