06:46:22  * muracquit (Read error: Connection reset by peer)
07:22:33  * ljharbquit (Ping timeout: 240 seconds)
07:24:07  * ljharbjoined
08:13:07  * zkatquit (Ping timeout: 250 seconds)
08:13:36  * zkatjoined
08:49:16  * targosjoined
10:31:45  * thealphanerdquit (Quit: farewell for now)
10:32:15  * thealphanerdjoined
13:47:01  * sgimenojoined
13:51:29  <sgimeno>Hi! Is it possible running the node-test-commit job for a commit in my node repository (not in the nodejs org)?
14:16:00  <jbergstroem>sgimeno: yes, you change the remote when you prepare the job
14:16:08  <jbergstroem>sgimeno: you an change remote, branch, etc
14:17:45  <sgimeno>jbergstroem, thanks! The thing is I tried this: https://ci.nodejs.org/job/node-test-commit/4288/ but didn't work
14:18:35  <sgimeno>I'm pretty sure I did it some time in the past but I must be missing something
14:18:44  <jbergstroem>looks like there are branch naming conflicts
14:18:49  <jbergstroem>some branch called 'backports'
14:18:58  <jbergstroem>try deleting it if you're not using it?
14:19:26  <sgimeno>jbergstroem, ok will do. Where did you see that info?
14:19:51  <jbergstroem>https://ci.nodejs.org/job/node-test-commit-plinux/3428/console
14:19:57  <jbergstroem>error: 'refs/remotes/origin/backport/6279' exists; cannot create 'refs/remotes/origin/backport'
14:20:23  <jbergstroem>i guess we need to figure out how often we want to scrub away remotes
14:20:29  <jbergstroem>but that is def the issue here at least
14:21:17  <sgimeno>great! Thanks!
14:21:28  <jbergstroem>np!
14:22:29  <sgimeno>Seems to be working now!!
14:23:30  <jbergstroem>great
16:10:15  <Trott>I'm not sure what's going on in this failure: https://ci.nodejs.org/job/node-test-binary-arm/3043/RUN_SUBSET=2,label=pi1-raspbian-wheezy/console
16:11:17  <Trott>I'd tag rvagg, but he's about 3 feet from me. Hi, Rod!
16:11:58  <rvagg>stupid jenkins error Trott, slave will need a restart
16:19:00  <jbergstroem>oh you're at a LAN PARTY now are you
16:19:06  <jbergstroem>got your coax cables out?
16:24:35  <jbergstroem>joaocgreis: so, with the clean stuff -- see above issue wrt sgimeno (duplicate branch names). should we start cleaning branches on post-completion? feels excessive..
16:29:06  <sgimeno>BTW, I've been running stress-single-test on win10 bots for the last couple of days. I've noticed the build process is really slow... to run a single test 10 times, the job takes 30-40 minutes... is this normal?
17:06:41  <Trott>Windows build failures seem to be happening all over in the last hour or so...
17:06:42  <Trott>https://ci.nodejs.org/job/node-compile-windows/3435/label=win-vs2013/console
17:06:58  <Trott>https://ci.nodejs.org/job/node-compile-windows/3436/label=win-vs2015/console
17:07:46  <Trott>Hmmm.. "all over" may have been an overstatement. There's a bunch going right now. Guess we'll see if any more fail...
17:43:31  <joaocgreis>jbergstroem: this is a different thing, this could always happen because it's changing the git remote. The only way to avoid this is to change to manual git as I did in the arms, because we don't have enough control over the git plugin
17:45:21  <joaocgreis>Trott: that was a dirty workspace but in the slaves (it has been common I think...) I cleaned those two, please mention me (write joaocgreis so my irccloud calls me) when you see failures in Windows machines
17:48:41  <joaocgreis>jbergstroem, rvagg: we talked about killing node (as in killall) at the beginning and end of runs before. Why didn't we do it? I was -0 on it but am changing to +1, I suspect it may be much more help than harm.
18:03:21  * node-ghjoined
18:03:21  * node-ghpart
21:18:07  * chorrelljoined
21:30:32  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)