00:25:02  * rmgjoined
00:30:06  * rmgquit (Ping timeout: 265 seconds)
02:25:46  * rmgjoined
02:30:56  * rmgquit (Ping timeout: 265 seconds)
06:27:20  * rmgjoined
06:32:45  * rmgquit (Ping timeout: 276 seconds)
08:51:35  * node-ghjoined
08:51:36  * node-ghpart
09:54:54  * bartosz__quit (Ping timeout: 260 seconds)
09:58:11  * bartosz__joined
10:24:08  * node-ghjoined
10:24:08  * node-ghpart
10:31:27  * thealphanerdquit (Quit: farewell for now)
10:31:58  * thealphanerdjoined
12:29:37  * rmgjoined
12:34:22  * rmgquit (Ping timeout: 260 seconds)
13:04:47  * evanlucasquit (Remote host closed the connection)
13:37:01  <phillipj>jbergstroem: sure 👍
14:12:42  * Fishrock123joined
14:16:40  * chorrelljoined
14:22:15  * chorrell_joined
14:23:32  * chorrellquit (Ping timeout: 276 seconds)
14:48:11  * chorrelljoined
14:50:28  * chorrell_quit (Ping timeout: 252 seconds)
14:55:08  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
14:59:57  * rmgjoined
16:07:46  * chorrelljoined
16:43:35  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:07:30  * Fishrock123quit (Read error: Connection reset by peer)
18:08:24  * Fishrock123joined
18:11:32  <orangemocha>rvagg do you have any updates with regards to the OSX sponsorship (https://github.com/nodejs/build/issues/367) based on the recommendations made by mikeal? At the last WG meeting we had discussed moving forward with asking the Foundation for money if nothing had happened by the next meeting (tomorrow). Of course, we can extend that if you need more time or
18:11:32  <orangemocha>think that are still more prospects to pursue.
18:44:37  <thealphanerd>orangemocha my tweet had close to 300k impressiosn and no one reached out
18:46:05  <thealphanerd>https://i.imgur.com/56el3IA.png
18:46:34  <thealphanerd>considering that many eyes saw it, and no one chimed in, I think it is safe to assume we might need to bring some money into the equation
18:55:40  * Fishrock123quit (Quit: Leaving...)
18:59:40  * Fishrock123joined
19:24:01  <orangemocha>roger that
19:35:26  <jbergstroem>:(
19:36:02  <jbergstroem>s/tested/supported/ even
19:36:30  <jbergstroem>if we're to form a list of supported os:es the lowest barrier is being able to test on it
21:18:14  <thealphanerd>yu
21:18:16  <thealphanerd>p
21:54:28  * rmgquit
22:03:00  * stefanmbjoined
22:10:35  <jbergstroem>thealphanerd: just retweeted you. reckon we're safe now :-D
22:10:55  <thealphanerd>phew
22:10:56  <thealphanerd>:p
22:15:51  * stefanmbquit (Quit: Textual IRC Client: www.textualapp.com)
22:15:59  <jbergstroem>thealphanerd: that moog you picked up is lots of fun. I used to have one but have moved onto stuff from mfb since
22:16:11  <thealphanerd>you had a mother32?
22:16:18  <thealphanerd>how long ago?
22:18:48  * rmgjoined
22:38:26  <jbergstroem>thealphanerd: i had a sample unit nov-dec last year. used to have a minimoog in the studio bakc in sweden
22:38:47  <thealphanerd>sample unit
22:38:48  <thealphanerd>dammmm
22:38:58  <thealphanerd>you some sort of moon light techno wizard :P
22:39:17  <thealphanerd>also linter stuff is acting weird
22:39:29  <thealphanerd>got multiple file fix in... but jenkins is not rendering the error information
22:39:30  <thealphanerd>https://ci.nodejs.org/job/node-test-linter/2516/tapResults/
22:44:02  <jbergstroem>thealphanerd: not very portable though :) i'm currently doing something smaller from mfb berlin -- fits better with my stuff; https://www.youtube.com/watch?v=JQIH7wooc6s
22:44:09  <jbergstroem>hm
22:44:11  <jbergstroem>will check
22:44:45  <jbergstroem>thealphanerd: are you referring to the broken table output?
22:44:50  <thealphanerd>yeah
22:44:59  <jbergstroem>that's a bug in the tap output generator
22:44:59  <thealphanerd>and the lack of error data in the main tap output
22:45:01  <jbergstroem>been around forever
22:45:13  <thealphanerd>it isn't rendering the yaml data
22:47:55  <jbergstroem>hm
22:48:34  <thealphanerd>makes the reporter kind of useless
22:48:42  <thealphanerd>did it use to work in the past?
22:49:09  <jbergstroem>yaml from tap13?
22:49:11  <jbergstroem>can't say i've tested
22:49:21  <jbergstroem>to be honest, the tap plugin is shit
22:49:29  <jbergstroem>it embeds all data in build.xml
22:49:43  <jbergstroem>its part of the reason jenkins is slow
22:49:54  <jbergstroem>(parse 20mb data for a pageview? sure_
22:50:20  <thealphanerd>lol
22:50:28  <thealphanerd>can we throw away jenkins
22:50:31  <thealphanerd>:D
22:58:06  <jbergstroem>if you build me a frontend to buildbot nine i'll set up the rest :)
22:58:22  <jbergstroem>it doesn't have all the ui stuff for orchestrating builds
22:59:25  <thealphanerd>link to buildbot nine?
23:01:14  * node-ghjoined
23:01:14  * node-ghpart
23:02:35  <jbergstroem>thealphanerd: this would be the 'reports' https://nine.buildbot.net/#/
23:03:04  <thealphanerd>jbergstroem your tweet worked
23:03:05  <thealphanerd>https://github.com/nodejs/build/issues/367#issuecomment-219573777
23:03:12  * node-ghjoined
23:03:12  * node-ghpart
23:03:22  <jbergstroem>wtf :-D
23:03:36  <thealphanerd>lolol
23:04:18  <jbergstroem>who needs 300k imps
23:08:24  * node-ghjoined
23:08:24  * node-ghpart
23:10:30  <jbergstroem>thealphanerd: trying to find you an architectural overview of buildbot nine. it's quite different than jenkins. more an api than anything else
23:10:42  <jbergstroem>and i don't think thir front facing stuff would be acceptable for us
23:10:44  <jbergstroem>*their
23:11:28  <jbergstroem>thealphanerd: Your Tweets earned 1.7K impressions over this 28 day period
23:11:40  <jbergstroem>Not sure about the conversion rate, but I think I'm ahead :)
23:11:53  <thealphanerd>heh
23:12:17  <thealphanerd>I'm sitting at 751k
23:12:21  <thealphanerd>nbd
23:12:22  <thealphanerd>:P
23:12:31  <jbergstroem>0/751000 whats it mean
23:13:03  <thealphanerd>so is the idea that buildbot 9 is an api we can use to automate this stuff... but we need a nice front end to actually audit the results?
23:15:39  <jbergstroem>what nine lacks in my opinion is: 1. a way for us to trigger builds; most buildbot projects just use vcs changes as trigger points. this requires us to build acl and trigger buttons. 2. a nicer build progress/report page; if you check the current ones, they're again not very optimised for human conusmption
23:16:34  <jbergstroem>the third thing that is fundamentally different is that jobs are defined in python, not edited through a ui. at this stage i'd even argue (language aside) that it would be a good thing for us since we could then introduce review for job changes.
23:17:00  <jbergstroem>besides that buildbot is just better in every regard; from stability to resource consumption to protocols
23:18:52  <thealphanerd>should we bring this up in the next build wg?
23:19:05  <thealphanerd>I'd be intersted in maybe moving citgm over as a trial or something like that
23:19:15  <jbergstroem>i think it belongs in the build-ng working group
23:19:39  <jbergstroem>at least until there's a few people heading in the same direction
23:19:43  <jbergstroem>the last comment in there referred to jenkins 2.
23:20:15  <thealphanerd>ah fair enough
23:20:20  <thealphanerd>is there movement on build-ng?
23:20:24  <jbergstroem>not really
23:20:44  <jbergstroem>i haven't been involved; feeling my input would be too one-sided. I just don't see any other alternative at the moment.
23:20:44  <thealphanerd>that was my impression too
23:20:45  <thealphanerd>:S
23:20:57  <thealphanerd>if you find some good docs let me kno
23:21:08  <thealphanerd>I'll dig in, and if I think a simple POC can be made I'll expllore
23:21:12  <thealphanerd>otherwise I'll make an issue
23:21:14  <jbergstroem>well, buildbot nine has tons of documentation
23:21:40  <jbergstroem>(the reason i keep referring to nine is because its a major bump from the current stable series)
23:22:37  <thealphanerd>:D
23:25:51  <jbergstroem>the up to date docs are here: http://buildbot.readthedocs.io
23:30:22  <jbergstroem>i think they're slowly adding angularjs stuff to abstract those things through the scheduler and www thing
23:39:10  * evanlucasjoined