00:18:13  <jbergstroem>this might be it: https://gist.github.com/jbergstroem/7ce0c159d1147e9469f32d1a5d553cce
00:20:03  * jenkins-monitor1quit (Remote host closed the connection)
00:20:03  * jenkins-monitorquit (Remote host closed the connection)
00:20:13  * jenkins-monitorjoined
00:20:13  * jenkins-monitor1joined
00:20:55  <jbergstroem>my head still hasn't wrapped how this happens on an LTS branch, security bump (patchlevel)
00:41:46  <thealphanerd>:(
01:15:57  <jbergstroem>i'm still none the wiser btw
01:18:10  <jbergstroem>just did this: https://github.com/nodejs/node/issues/6706
01:28:46  <jbergstroem>https://issues.jenkins-ci.org/browse/JENKINS-25791?focusedCommentId=256264&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-256264
01:44:40  <jbergstroem>most recent issues in their jira both touches on similar issues
01:46:03  <jbergstroem>oh, _my_ last recent..
01:46:05  <jbergstroem>sigh
02:13:00  <rvagg>I got this working again http://memtest.nodejs.org/dashboard/db/memtest
02:13:04  <rvagg>simplified some of the setup
02:13:09  <rvagg>works betterer now
02:13:19  <rvagg>http://memtest.nodejs.org gets you there, no need for the full url
02:16:34  <jbergstroem>sweet
02:16:41  <jbergstroem>now all you have to do is get jenkins going :-D
02:17:03  <jbergstroem>ah, didn't grafana 3 get out just now
02:19:11  <jbergstroem>we should hook up benchmark results to grafana too?
02:19:34  <jbergstroem>what do you use for storage?
02:45:57  <rvagg>InfluxDB
02:46:14  <rvagg>The grafana 3 announcement reminded me to fix this up
02:48:58  <jbergstroem>influx/grafana is a great combo
02:49:00  <jbergstroem>we use it heavily
03:57:46  * evanlucasjoined
04:50:24  * rmgquit (Remote host closed the connection)
04:50:59  * rmgjoined
04:55:16  * rmgquit (Ping timeout: 250 seconds)
05:29:03  * node-ghjoined
05:29:03  * node-ghpart
05:32:03  * node-ghjoined
05:32:03  * node-ghpart
05:37:21  * node-ghjoined
05:37:22  * node-ghpart
05:38:28  <rvagg>TIL ^ find does nested conditions
05:51:32  * rmgjoined
05:55:56  * rmgquit (Ping timeout: 250 seconds)
06:27:45  * node-ghjoined
06:27:46  * node-ghpart
06:32:38  <Trott>Regarding CI, no change in the last few hours, right? It's not working right now, it's being looked into, and there's no ETA because if we knew what exactly was wrong then it would probably be fixed already. Is all that more-or-less correct?
06:33:33  <jbergstroem>no change
06:33:44  <jbergstroem>its being looked into between me and rod
06:33:58  <jbergstroem>we're trying to split hours spent
06:34:27  <jbergstroem>the TL;DR is prdy much this: https://gist.github.com/jbergstroem/369f02d10ba8643989f89c0c0ea90143
06:36:56  <Trott>Cool. Thanks for all the hard work. Sorry it's probably ruining your day. :-|
07:10:47  * node-ghjoined
07:10:47  * node-ghpart
10:01:14  <rvagg>I'll be back on it shortly, finishing family stuff
10:50:11  * thealphanerdquit (Quit: farewell for now)
10:50:41  * thealphanerdjoined
13:11:26  <jbergstroem>thealphanerd: you around?
13:14:51  * node-ghjoined
13:14:52  * node-ghpart
13:16:02  * node-ghjoined
13:16:02  * node-ghpart
13:25:03  * Fishrock123joined
13:25:09  <jbergstroem>thealphanerd: me/rvagg is signing off but if you get to running other jobs that fail just ping me and i'll add the environment vars tomorrow
13:27:32  <sgimeno>jbergstroem, is still CI unavailable?
13:27:43  <jbergstroem>sgimeno: no its coming back just now
13:27:53  <jbergstroem>sgimeno: looking at 2 builds complete. seems fine
13:28:29  <sgimeno>jbergstroem, great! thanks for fixing it!
13:30:27  <jbergstroem>sgimeno: \o/ not just me though -- multiple people from the build group was involved!
13:31:07  <sgimeno>thanks everyone then :)
13:32:16  <Fishrock123>jbergstroem: just curious, did you disable the PR Status? No rush but I found it odd it didn't even work when I told the CI to not rebase
13:32:54  <jbergstroem>Fishrock123: yeah i need to change the var check. didn't want that as another source of problems when we had a security release to coordinate. i'll reintroduce it tomorrow and likely put some work into it
13:33:02  <Fishrock123>ah
13:33:10  <Fishrock123>cool, thanks!
13:34:26  <jbergstroem>np :) keen on getting it going
13:59:24  <sgimeno>There was this problem on one of the w10 bots: https://ci.nodejs.org/job/node-test-binary-windows/2093/RUN_SUBSET=3,VS_VERSION=vcbt2015,label=win10/console
15:12:58  * node-ghjoined
15:12:59  * node-ghpart
15:13:28  * node-ghjoined
15:13:29  * node-ghpart
15:19:11  * node-ghjoined
15:19:11  * node-ghpart
15:56:56  * rmgjoined
16:19:16  * node-ghjoined
16:19:16  * node-ghpart
16:20:40  * node-ghjoined
16:20:41  * node-ghpart
16:22:51  * node-ghjoined
16:22:51  * node-ghpart
16:23:41  * node-ghjoined
16:23:41  * node-ghpart
17:12:19  <thealphanerd>hey all... it looks like the CI for libuv might be down after the upgrades yesterday. /cc jbergstroem michael___
18:21:03  * Fishrock123quit (Remote host closed the connection)
18:46:34  <michael___>orangemocha what I remembered was that 354 needed more discussion in the PR but I don't see that anybody has commented so leaving on the agenda as a reminder might make sense
18:50:25  * Fishrock123joined
18:58:07  <thealphanerd>jbergstroem it looks like citgm is down too --> https://ci.nodejs.org/view/Node.js-citgm/job/thealphanerd-smoker/263/nodes=osx1010/console
18:59:09  <thealphanerd>looks like something to do with --> hudson4544871683749908337.sh
19:02:18  <thealphanerd>jbergstroem I think we missed a couple of env vars in there
19:02:51  * node-ghjoined
19:02:54  * node-ghpart
19:04:58  <thealphanerd>going to privately message you the missing keys
20:23:45  <jbergstroem>i've added all missing keys i could find in the log
20:24:08  <jbergstroem>just gotta wait for all open jobs to finish
20:26:45  <jbergstroem>looks like windows slaves are stuck?
20:44:18  <Fishrock123>jenkins going to shut down?
21:05:44  <jbergstroem>yes
21:05:49  <jbergstroem>i need to restart
21:14:57  <jbergstroem>ok, restarted
21:15:02  * jenkins-monitor1quit (Remote host closed the connection)
21:15:03  * jenkins-monitorquit (Remote host closed the connection)
21:15:12  * jenkins-monitor1joined
21:15:13  * jenkins-monitorjoined
21:16:07  <jbergstroem>Fishrock123: should be good to go
22:48:52  <thealphanerd>jbergstroem looks like citgm + v8 ci is working again
22:48:56  <thealphanerd>thanks
22:48:59  <jbergstroem>thealphanerd: sweet
22:49:11  <thealphanerd>should we be looking at a way to implement that doesn't use env vars?
22:58:06  <jbergstroem>lets do it if it becomes painful down the road?
22:58:18  <jbergstroem>i mean the downtime yesterday wasn't about env
22:58:25  <jbergstroem>ci-release just did a nightly btw, all good
23:12:04  <thealphanerd>sgtm
23:21:50  <thealphanerd>jbergstroem super weird failure on osx https://ci.nodejs.org/view/Node.js-citgm/job/thealphanerd-smoker/264/nodes=osx1010/
23:22:19  <thealphanerd>node vanished off the system part way through
23:22:21  <thealphanerd>wat
23:22:21  <thealphanerd>!
23:22:50  <jbergstroem>that folder should never go ever
23:22:55  <jbergstroem>wonder if its tsomething else
23:23:03  <jbergstroem>let me check so ti doesn't run stuff in parallel
23:23:06  <jbergstroem>otherwise classic jenkins writeoff
23:24:47  <jbergstroem>yeah both looks ok :/
23:25:09  <jbergstroem>i don't have access; perhaps @rvagg can log in later and see if something's going on.
23:35:13  * Fishrock123quit (Quit: Leaving...)