00:31:07  * Fishrock123joined
01:27:47  * Fishrock123quit (Remote host closed the connection)
01:42:32  * Fishrock123joined
02:25:30  * Fishrock123quit (Remote host closed the connection)
02:44:49  <Trott>rvagg jbergstroem: test-nodesource_ceejbot-debian7-arm_pi1p-1 now blowing up. https://ci.nodejs.org/job/node-test-binary-arm/3576/RUN_SUBSET=addons,label=pi1-raspbian-wheezy/ https://ci.nodejs.org/job/node-test-binary-arm/3576/RUN_SUBSET=0,label=pi1-raspbian-wheezy/ https://ci.nodejs.org/job/node-test-binary-arm/3575/RUN_SUBSET=0,label=pi1-raspbian-wheezy/
02:44:49  <Trott>etc.
02:45:07  <jbergstroem>Trott: yeah me/rod is aware; tryna figure it out
02:45:21  <jbergstroem>nfs issues
02:45:39  <Trott>Ah, OK. I thought that was a new one. I thought earlier it was test-nodesource_ceejbot-debian7-arm_pi1p-1
02:45:49  <Trott>Oh, wait, yeah, that is the same one. Uh, never mind. :-(
03:09:31  * Fishrock123joined
03:24:41  <rvagg>Trott: thanks, it was taken offline ~30 minutes after those failures, still working on it https://ci.nodejs.org/computer/test-nodesource_ceejbot-debian7-arm_pi1p-1/
03:54:36  * node-ghjoined
03:54:36  * node-ghpart
03:55:11  * node-ghjoined
03:55:11  * node-ghpart
03:59:09  * node-ghjoined
03:59:09  * node-ghpart
04:01:10  * Fishrock123quit (Quit: Leaving...)
05:42:49  * jenkins-monitorquit (Remote host closed the connection)
05:43:00  * jenkins-monitorjoined
05:53:45  <rvagg>I've reconnected nfs on test-nodesource_ceejbot-debian7-arm_pi1p-1 and it _looks_ OK so it's back in the cluster, we'll see
06:00:52  * node-ghjoined
06:00:52  * node-ghpart
06:03:29  <phillipj>gah github squash fail ^
06:03:42  <phillipj>ended up as two commits, even tho I used the squash button
06:04:53  <phillipj>might be cause I gpg signed my commits lately and those commits cannot be squashed from the github ui
06:05:14  <ljharb>wait really? github won't squash gpg-signed commits?
06:05:32  <ljharb>so if i gpg-sign my commits nobody can screw them up by squashing them? :-D
06:05:45  <starefossen>makes sense if think about it
06:06:06  <starefossen>but should be communicated to the user
06:06:55  <starefossen>well, they can (if they do it manually) but then the resulting commit will no longer be signed by you
06:07:26  <starefossen>s/signed/gpg-signed/
06:07:47  <ljharb>sure, but i'm not worried about people doing the wrong thing on the CLI
06:08:01  <ljharb>but the github UI makes it really easy to destroy valuable commit granularity
06:09:08  <starefossen>true
06:27:27  <phillipj>yeah would have been nice to get a warning about what was going to happen
06:28:14  <phillipj>cant seem to find those two commits in the git log either
06:29:07  <phillipj>thought I'd rebase/push one of those commits away, but my interactive rebase doesn't list the commit gh created :/
06:53:29  * node-ghjoined
06:53:29  * node-ghpart
08:19:18  * sgimenojoined
10:37:10  * thealphanerdquit (Quit: farewell for now)
10:37:41  * thealphanerdjoined
11:16:50  <rvagg>Trott: something to keep an eye on with the clang 3.4.1 CI nodes running tests, I think they might be consistently failing two tls tests: https://ci.nodejs.org/job/node-test-commit-linux/4909/nodes=ubuntu1204-clang341-64/console - test-https-connect-address-family & test-tls-connect-address-family
11:17:27  <rvagg>Trott: currently master and v6 is not working with clang 3.4.1 as per https://github.com/nodejs/node/issues/8323 but assuming that gets fixed this could be the next barrier to keeping those nodes in the mix but we need more data
11:41:31  <rvagg>Trott: I take that back, it's all about the ipv6 ::1 stuff, https://github.com/nodejs/build/issues/415, fixing that on all the ubuntu12 hosts fixes it for clang 3.4.1 and it's green for v4.x
12:56:22  * lanceballchanged nick to lance|afk
12:56:51  * lance|afkchanged nick to lanceball
13:33:47  * gibfahnjoined
13:36:43  * node-ghjoined
13:36:43  * node-ghpart
13:38:29  <jbergstroem>i'll fix the remaining hosts re ipv6
13:40:02  <jbergstroem>looks like rod beat me to it
13:58:36  * node-ghjoined
13:58:36  * node-ghpart
14:07:25  * node-ghjoined
14:07:26  * node-ghpart
14:26:03  * Fishrock123joined
14:39:20  <Trott>I guess the consistent https://ci.nodejs.org/job/node-test-commit-linux/nodes=ubuntu1204-clang341-64 failure is a WIP? Most recent example: https://ci.nodejs.org/job/node-test-commit-linux/nodes=ubuntu1204-clang341-64/4912/console
14:39:40  <Trott>Whoops, should be "consistent ubuntu1204-clang341-64 failure" but you get the idea.
14:45:01  * node-ghjoined
14:45:01  * node-ghpart
14:57:41  <jbergstroem>hm
14:57:46  <jbergstroem>it doens't oom
16:40:03  * Fishrock123quit (Remote host closed the connection)
17:26:14  * gibfahnquit (Ping timeout: 264 seconds)
17:41:16  * Fishrock123joined
17:44:59  * lanceballchanged nick to lance|afk
17:46:03  * Fishrock123quit (Ping timeout: 276 seconds)
17:49:59  * Fishrock123joined
18:02:00  <mhdawson>FYI the offline ppc machines are because we are transitioning to new ones. I've added the new ones and then disabled the old ones to force builds over
18:02:15  <mhdawson>will delete them once we are confident new ones are working as epxected
18:18:12  <jbergstroem>👌🏻
18:52:58  * lance|afkchanged nick to lanceball
21:02:25  * node-ghjoined
21:02:25  * node-ghpart
21:08:10  * node-ghjoined
21:08:10  * node-ghpart
21:09:15  * node-ghjoined
21:09:15  * node-ghpart
21:09:25  * node-ghjoined
21:09:25  * node-ghpart
21:09:35  * node-ghjoined
21:09:35  * node-ghpart
21:13:37  * node-ghjoined
21:13:37  * node-ghpart
21:14:58  * node-ghjoined
21:14:58  * node-ghpart
21:16:15  * lanceballchanged nick to lance|afk
21:33:29  * node-ghjoined
21:33:29  * node-ghpart
22:51:45  * node-ghjoined
22:51:45  * node-ghpart
22:52:03  * node-ghjoined
22:52:03  * node-ghpart
23:00:46  * Fishrock123quit (Remote host closed the connection)