00:30:35  * jasnellquit (Ping timeout: 240 seconds)
00:38:33  * Fishrock123joined
00:43:20  * Fishrock123quit (Ping timeout: 255 seconds)
00:58:09  * Fishrock123joined
01:20:07  <Trott>Taking test-azure_msft-win2012r2-x64-1 offline for repeated build failures. Probably needs a workspace clean too? (Maybe I should learn how to do that myself?) refack joaocgreis
01:20:28  <Trott>Sample failure: https://ci.nodejs.org/job/node-test-binary-windows/COMPILED_BY=vs2015-x86,RUNNER=win2012r2,RUN_SUBSET=0/12290/console
01:20:50  <Trott>https://www.irccloud.com/pastebin/ts0XQaYL/
01:28:26  <refack>Check newer builds
01:29:09  <refack>The binary git repo grew to 76GB. i cleaned it 2 hours ago
01:30:48  <Trott>That build is from 1 hour 27 minutes ago.
01:30:57  <Trott>test-rackspace-freebsd10-x64-1 seems stalled out too.
01:31:16  <Trott>https://ci.nodejs.org/job/node-test-linter/13013/console
01:31:17  <refack>I'll look into that one
01:31:30  <Trott>https://www.irccloud.com/pastebin/AZFUe0NL/
01:31:49  <Trott>It is the lint host so lint keeps stalling. :-/
01:32:22  <Trott>https://ci.nodejs.org/job/node-test-linter/13015/ is a stalled lint job that's still in progress. So you can investigate things in action if that helps. Not sure if it does.
01:32:26  <refack>I saw one of that earlier. Thought it was a one off
01:32:52  <Trott>Three in a row, four if you count the one that's running now. Here's the build history: https://ci.nodejs.org/computer/test-rackspace-freebsd10-x64-1/builds
01:33:06  <refack>I run 'git gc' on it...
01:33:32  <Trott>(Should I put that Windows host back online? Or did you want to look at that first?)
01:33:59  <refack>I'll look at that host
01:34:28  <Trott>OK, I'll leave it offline then. Thanks for all your help.
01:36:40  * Fishrock123quit (Remote host closed the connection)
01:37:00  * Fishrock123joined
01:37:28  * Fishrock123quit (Remote host closed the connection)
01:48:40  * Fishrock123joined
01:49:39  * Fishrock123quit (Remote host closed the connection)
01:56:48  * Fishrock123joined
02:34:29  * Fishrock123quit (Quit: Leaving...)
04:44:02  * joyeejoined
04:57:55  * joyee_joined
05:01:23  * joyeequit (Ping timeout: 258 seconds)
05:32:53  * jasnelljoined
06:00:45  * jasnellquit
06:09:52  * joyee_quit (Remote host closed the connection)
06:38:28  * joyeejoined
09:26:08  * seishunjoined
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:42  * mylesborinsjoined
10:43:05  * joyeequit (Remote host closed the connection)
10:43:33  * joyeejoined
10:45:29  * joyeequit (Remote host closed the connection)
10:45:35  * joyeejoined
13:26:17  * joyeequit (Remote host closed the connection)
13:26:51  * joyeejoined
13:38:07  * joyee_joined
13:39:45  * joyee_quit (Remote host closed the connection)
13:40:13  * joyee_joined
13:41:27  * joyeequit (Ping timeout: 260 seconds)
13:44:35  * joyee_quit (Ping timeout: 240 seconds)
13:48:22  * node-ghjoined
13:48:22  * node-ghpart
14:12:07  * node-ghjoined
14:12:07  * node-ghpart
14:13:05  * seishunquit (Ping timeout: 252 seconds)
14:13:55  * node-ghjoined
14:13:55  * node-ghpart
14:19:11  * node-ghjoined
14:19:11  * node-ghpart
14:20:21  * seishunjoined
14:31:31  * node-ghjoined
14:31:31  * node-ghpart
14:32:47  * node-ghjoined
14:32:47  * node-ghpart
14:34:58  * node-ghjoined
14:34:58  * node-ghpart
14:36:18  * node-ghjoined
14:36:18  * node-ghpart
14:37:41  * node-ghjoined
14:37:41  * node-ghpart
14:41:01  <Trott>refack: Is that all there is to cleaning a workspace? Shoot, that's easy, I can do that! :-D
14:41:22  <Trott>I thought it involved connecting with some remote desktop software and knowing what you're doing on the system or something like that.
14:41:32  <refack>It's a race, since the job has to be on top
14:41:47  <Trott>Ah, I see.
14:42:40  <refack>So for the test-binary it's a whack-a-mole since there are ~20 sub jobs
14:43:51  <refack>Also if there's an undead `git` process the Jenkins command _will_ timeout
14:45:52  <refack>So in the last hour or so I got ~50% success (the rest I had to remote-desktop and "know what I'm doing")
14:51:25  <Trott>Looking pretty good so far over in https://ci.nodejs.org/job/node-test-binary-windows/12319/ based on a spot check.
15:20:07  * joyeejoined
16:40:40  * node-ghjoined
16:40:40  * node-ghpart
16:40:55  * node-ghjoined
16:40:55  * node-ghpart
16:43:06  * node-ghjoined
16:43:06  * node-ghpart
16:49:14  * node-ghjoined
16:49:14  * node-ghpart
17:33:28  * node-ghjoined
17:33:28  * node-ghpart
17:40:26  <refack>Trott: 12952 just finished green
17:59:11  * seishunquit (Remote host closed the connection)
17:59:49  * seishunjoined
18:06:15  <Trott>refack: Yup! Now to figure out what's up with the Raspberry Pi failures...
18:06:22  <Trott>...or at least remove the problematic ones from the rotation...
18:06:26  <refack>Same
18:06:40  <refack>(they sync with the huge temp binary git)
18:07:29  <Trott>Took test-requireio_davglass-debian7-arm_pi1p-1 offline because it's the one that failed a dozen or so times in a row....
18:08:02  <Trott>Ping rvagg joaocgreis ^^^^^
18:08:16  <Trott>Trying again hoping for green... https://ci.nodejs.org/job/node-test-binary-arm/11317/
18:24:13  * joyeequit (Remote host closed the connection)
18:30:15  * joyeejoined
18:34:42  * joyeequit (Client Quit)
18:56:09  * tniessenjoined
19:47:27  * tniessenquit (Remote host closed the connection)
19:47:44  * tniessenjoined
19:54:48  * seishunquit (Ping timeout: 240 seconds)
19:55:02  <Trott>Green!
20:12:53  <Trott>Also took test-requireio_pivotalagency-debian8-arm_pi3-2 offline. rvagg joaocgreis
20:24:20  * seishunjoined
20:56:10  * seishunquit (Ping timeout: 264 seconds)
22:32:37  <refack>I think the arm issues are solved (since they all use a shared local minror)
22:33:41  <refack>Windows salves are a PITA to clean, so maybe joaocgreis could add a clean step to the job script
23:48:42  * mylesborinsquit (Ping timeout: 260 seconds)
23:51:22  * mylesborinsjoined