00:34:18  * jenkins-monitor1quit (Remote host closed the connection)
00:34:28  * jenkins-monitor1joined
00:34:33  * jenkins-monitorquit (Remote host closed the connection)
00:34:42  * jenkins-monitorjoined
01:02:08  * jenkins-monitor1quit (Remote host closed the connection)
01:02:19  * jenkins-monitor1joined
01:02:23  * jenkins-monitorquit (Remote host closed the connection)
01:02:43  * jenkins-monitorjoined
01:32:56  <jbergstroem>orangemocha: another thing worth noticing: we haven't had any problems with plugin updates since the multijob stuff
01:47:15  <jbergstroem>java chillaxing at good 'ol 1200% cpu (12 core system)
01:48:32  <jbergstroem>out of ra
01:48:33  <jbergstroem>m
01:48:36  <jbergstroem>on a 32G machine.
01:50:09  <jbergstroem>jmap even throws exceptions :-D
02:17:29  <jbergstroem>ok, most pages are just not responding so i'll restart. ping thealphanerd (your test will die)
02:17:45  <thealphanerd>sigh
02:17:46  <thealphanerd>ok
02:17:47  <thealphanerd>:(
02:17:50  <thealphanerd>:P
02:18:18  <thealphanerd><3
02:20:01  * jenkins-monitorquit (Remote host closed the connection)
02:20:02  * jenkins-monitor1quit (Remote host closed the connection)
02:20:10  * jenkins-monitorjoined
02:20:11  * jenkins-monitor1joined
05:12:55  * evanlucasquit (Ping timeout: 246 seconds)
05:31:27  <Trott>Anything up with smartos14-64 or are all those test failures lately really a test thing and not an infra problem?
05:35:35  <jbergstroem>i added JOBS= to them
05:36:03  <jbergstroem>~2w ago ish?
06:00:46  <phillipj>jbergstroem: the jenkins/completion issues you mentioned.. we got error reports when doing the initial tests e.g. https://github.com/nodejs/node/pull/6674
06:01:30  <jbergstroem>phillipj: yeah. the post-exec jobs are just annoying. I either don't understand it or its unreliable
06:01:39  <jbergstroem>trying to just get a "execute shell" and do the logic myself
06:02:25  <phillipj>okey, so they're unstable as is atm?
06:02:42  <jbergstroem>phillipj: btw, evanlucas and I spoke about commit message formatting a few days ago. We came up with a strategy to avoid even checking out via git, so it'll be pretty quick
06:02:56  <jbergstroem>i wouldn't trust it, no. just leave it until i get a better look
06:03:03  <jbergstroem>was doing it this morning then jenkins just went to bed
06:03:19  <phillipj>oh alright..
06:03:30  <jbergstroem>wsa thinking we could just leave the commit message as 'pending' (but change message) until we get the proper metadata, then either fail or pass
06:04:04  <jbergstroem>it'd be the first job we would likely run on all commits
06:05:43  <jbergstroem>Trott: actually, come to think of it they likely already had JOBS in there
06:08:08  <phillipj>jbergstroem: sgtm
06:09:42  <phillipj>IIRC the payload we get from github webhooks provides metadata about the related commits, so we might not have to do additional gh.com requests
06:11:09  <jbergstroem>if we get the full stream from gh we're just fine
06:11:14  <jbergstroem>we'll get what commits attaches to prs
08:42:08  * michael____joined
08:42:37  * rvagg__joined
08:42:57  * starefossen_joined
08:43:41  * phillipj_joined
08:45:40  * phillipjquit (Ping timeout: 250 seconds)
08:45:41  * starefossenquit (Ping timeout: 250 seconds)
08:45:42  * michael___quit (Ping timeout: 250 seconds)
08:45:43  * rvaggquit (Ping timeout: 250 seconds)
08:46:02  * phillipj_changed nick to phillipj
08:46:02  * starefossen_changed nick to starefossen
08:46:18  * michael____changed nick to michael___
08:46:30  * rvagg__changed nick to rvagg
08:48:18  * zkatquit (Ping timeout: 244 seconds)
08:50:15  * orangemochaquit (Ping timeout: 276 seconds)
08:58:18  * orangemochajoined
08:59:38  * zkatjoined
09:16:53  * node-ghjoined
09:16:53  * node-ghpart
09:17:58  * node-ghjoined
09:17:59  * node-ghpart
09:26:14  * joaocgreisquit (Ping timeout: 260 seconds)
09:29:19  * joaocgreisjoined
09:36:44  * othiym23quit (Ping timeout: 260 seconds)
09:36:44  * Trottquit (Ping timeout: 260 seconds)
09:40:32  * othiym23joined
09:40:33  * Trottjoined
10:13:16  * node-ghjoined
10:13:16  * node-ghpart
10:47:12  * thealphanerdquit (Quit: farewell for now)
10:47:42  * thealphanerdjoined
11:57:05  * evanlucasjoined
12:12:01  * node-ghjoined
12:12:01  * node-ghpart
12:31:15  * node-ghjoined
12:31:15  * node-ghpart
13:04:17  * evanlucasquit (Remote host closed the connection)
13:13:32  * evanlucasjoined
13:14:32  * node-ghjoined
13:14:32  * node-ghpart
13:24:23  * evanlucasquit (Remote host closed the connection)
13:34:02  * evanlucasjoined
13:34:13  * node-ghjoined
13:34:14  * node-ghpart
14:17:47  * chorrelljoined
14:25:22  <phillipj>there's no dummies guide to get the ansible build setup going, right?
14:26:24  <phillipj>I've got no ansible experience, but would really like to git especially nodejs.org running to debug some nginx things
14:26:43  <phillipj>s/git/get
14:45:12  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
14:45:33  * chorrelljoined
15:13:10  * stefanmb_joined
15:16:06  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
15:45:04  <thealphanerd>phillipj running locally or on a dev server kind of thing?
15:48:08  <phillipj>thealphanerd: locally
15:49:30  <thealphanerd>kk I have little ansible experience too... but can maybe dig in a bit later to see about maybe getting it running in a docker container locally or something
15:58:08  * jbergstroemtopic: we're the nodejs build group. https://ci.nodejs.org https://github.com/nodejs/build -- irc logs: http://logs.libuv.org/node-build/latest
15:58:35  * jbergstroemtopic: we're the nodejs build group. https://ci.nodejs.org https://github.com/nodejs/build -- irc logs: http://logs.libuv.org/node-build/latest
16:05:48  <phillipj>thanks, a couple of pointers in the right direction would be awesome
16:08:34  <phillipj>tried a month or two ago, but stumpled upon some wierd things which made me jump onto something else in my backlog :)
16:09:43  <phillipj>now I ofc don't even remember what those issues were
17:05:15  * stefanmb_changed nick to stefanmb
17:35:25  * stefanmb_joined
17:36:49  * stefanmbquit (Ping timeout: 260 seconds)
17:40:56  * chorrelljoined
17:43:13  * stefanmbjoined
17:45:05  * stefanmb_quit (Ping timeout: 260 seconds)
17:58:34  * ofrobotsjoined
17:59:51  <ofrobots>orangemocha: I am trying to build node on a fresh windows VM with Visual Studio community 2015. `vcbuild.bat` is unable to detect my version of visual studio
18:00:10  <ofrobots>is Visual Studio Community suitable for building Node, or do I need to get a different flavour?
18:03:40  <ofrobots>ultimately the problem is vcbuild.bat is looking for vcvarsall.bat in %VS140COMNTOOLS%\..\..\vc as a check for whether Visual Studio is installed. Visual Studio Community 2015 doesn't seem to contain this file.
18:18:59  <phillipj>ofrobots: pretty sure I've got VS community 2015 on a win10 working
18:20:18  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
18:21:04  <phillipj>did you check the c++ options while installing VS?
18:21:58  * chorrelljoined
18:33:36  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:35:47  <ofrobots>phillipj: I did the default install - that's probably the problem - thanks.
18:39:29  * Fishrock123joined
21:24:50  <orangemocha>ofrobots, community 2015 is definitely supported
21:24:52  <orangemocha>https://github.com/nodejs/node/blob/master/BUILDING.md#windows
21:25:02  <ofrobots>I have it working now, thanks!
21:25:21  <orangemocha>guessing you probably needed a new cmd windows to get the updated environment
21:25:23  <ofrobots>working on getting v8-inspector working on windows now
21:25:31  <orangemocha>great!
21:30:04  * stefanmbquit (Quit: My Mac has gone to sleep. ZZZzzz…)
21:49:12  <ofrobots>How would I go about getting access to a SmartOS build machine?
22:09:32  * stefanmbjoined
22:17:34  <thealphanerd>ofrobots I believe those are provided to us by joyent
22:17:37  <thealphanerd>but I ciould be mistaken
22:22:09  <jbergstroem>ofrobots: sure; which one? 64-bit or 32?
22:23:16  <ofrobots>jbergstroem: let's start with 64-bit. Hopefully that's all I need.
23:08:37  * stefanmbquit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:58:01  * node-ghjoined
23:58:01  * node-ghpart
23:58:51  * stefanmbjoined