00:19:27  * michael___joined
00:21:39  * rmgjoined
00:22:25  * othiym23joined
00:23:22  * bret_joined
00:26:30  * rmgquit (Ping timeout: 260 seconds)
02:23:25  * rmg_joined
02:27:50  * rmg_quit (Ping timeout: 260 seconds)
03:27:58  * indutnypart ("Textual IRC Client: www.textualapp.com")
04:49:07  <jbergstroem>thealphanerd: i'll spawn another ubuntu12 64-bit shortly
05:25:25  * rmg_joined
05:30:19  * rmg_quit (Ping timeout: 252 seconds)
06:14:13  * 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
06:14:57  <thealphanerd>thanks jbergstroem
06:15:14  * bartosz__quit (Ping timeout: 260 seconds)
06:16:29  * bartosz__joined
06:19:19  * zkatquit (Ping timeout: 260 seconds)
06:19:54  * benglquit (Ping timeout: 260 seconds)
06:20:45  * bengljoined
06:21:39  * starefossenquit (Ping timeout: 260 seconds)
06:23:21  * zkatjoined
06:23:24  * Trottquit (Ping timeout: 260 seconds)
06:24:02  * starefossenjoined
06:25:52  * Trottjoined
07:27:02  * rmgjoined
07:31:45  * rmgquit (Ping timeout: 260 seconds)
07:51:04  * sgimenojoined
08:58:50  * node-ghjoined
08:58:50  * node-ghpart
09:07:17  * node-ghjoined
09:07:17  * node-ghpart
09:08:09  * node-ghjoined
09:08:09  * node-ghpart
09:28:27  * rmgjoined
09:33:24  * rmgquit (Ping timeout: 276 seconds)
10:27:37  * thealphanerdquit (Quit: farewell for now)
10:28:08  * thealphanerdjoined
12:31:13  * rmgjoined
12:35:53  * rmgquit (Ping timeout: 244 seconds)
13:48:40  * Fishrock123joined
14:42:37  * jenkins-monitorquit (*.net *.split)
15:32:41  * jenkins-monitorjoined
15:33:44  * rmgjoined
15:33:59  * Fishrock123quit (Remote host closed the connection)
15:38:37  * rmgquit (Ping timeout: 252 seconds)
15:44:31  * chorrelljoined
15:45:10  * jenkins-monitorquit (*.net *.split)
15:45:56  * jenkins-monitorjoined
15:57:31  * rmgjoined
15:57:33  * jenkins-monitorquit (*.net *.split)
16:05:41  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
16:06:19  * jenkins-monitorjoined
16:35:12  * chorrelljoined
16:51:25  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
18:06:17  * Fishrock123joined
18:20:29  <Fishrock123>how can I force jenkins not to 504 for long requests?
18:20:34  <Fishrock123>e.g. https://ci.nodejs.org/job/node-test-commit-linux/3513/nodes=ubuntu1604-64/tapTestReport/
18:21:09  <Fishrock123>oh my god I hate jenkins
18:29:07  <thealphanerd>Fishrock123 I KNOW!
18:29:53  <thealphanerd>I'm thinking about trying to do some sort of pilot project for citgm on alternative back end
18:30:06  <thealphanerd>also Ben Coe from npm is talking to the travis folks about stuff
18:30:25  <thealphanerd>I think we should be chatting with them... word is most of the stuff they are testing these days is node
18:31:24  <jbergstroem>orangemocha, rvagg: you's around?
18:31:28  <Fishrock123>thealphanerd: I don't think travis would be configureable enought hough?
18:31:40  <thealphanerd>Generally I'd agree
18:31:47  <jbergstroem>Fishrock123: tap reports are slooooow
18:31:50  <thealphanerd>but they might have stuff we can use that isn't exactly their public offering
18:31:57  <Fishrock123>jbergstroem: everything is slow..
18:32:06  <jbergstroem>thealphanerd: we don't test node though, we test c++ :-D
18:32:09  <thealphanerd>citgm is especially slow due to how massive the tap output is
18:32:24  <thealphanerd>jbergstroem I meant more in the sense that they have an inherit need for node to be stable
18:32:33  <jbergstroem>thealphanerd: sure
18:32:40  <thealphanerd>thinking osx boxes :P
18:32:58  <Fishrock123>I wonder if anyone thinks we should still seriously look into node.js alternatives
18:32:58  <jbergstroem>thealphanerd: yeah we're making progress on that front. hopefully have a response in a few days
18:33:07  <Fishrock123>I'm tied up for thext while still though
18:33:10  <jbergstroem>Fishrock123: ah. just out of ram
18:33:16  <jbergstroem>28G not enough
18:33:20  <Fishrock123>what
18:33:33  <Fishrock123>jbergstroem: 28gb ram isn;t enough for... the tap report?
18:33:35  <thealphanerd>Fishrock123 node.js alternatives?
18:33:36  <Fishrock123>that isn't possible
18:33:40  <jbergstroem>Fishrock123: for jenkins
18:33:42  <thealphanerd>Ahh
18:33:53  <thealphanerd>I was going to maybe do some experiments with build bot
18:33:54  <jbergstroem>I'll restart jenkins as soon as jobs finish
18:33:56  <Fishrock123>thealphanerd: this stuff: https://github.com/nodejs/Future-CI
18:34:09  <Fishrock123>yeah
18:34:10  <thealphanerd>I think starting from first principals is going to be a nightmare
18:34:14  <jbergstroem>Fishrock123: a few of us might be into giving buildbot nine a go
18:34:24  <Fishrock123>problem with buildbot is it;s lots of programming and in python
18:34:26  <thealphanerd>python > java st least
18:34:33  <Fishrock123>more people would be willing to do lots of programming node lol
18:34:37  <Fishrock123>yeah, it;s a step
18:34:51  <Fishrock123>jbergstroem: rvagg mentioned we'd need to amke our own frontend then, right?
18:34:55  <jbergstroem>Fishrock123: 1. not lots and 2. i think at this stage checking jobs in instead of having them in input forms is an improvements
18:34:57  <jbergstroem>-s
18:35:09  <Fishrock123>true
18:35:27  <jbergstroem>Fishrock123: well that was kind of my words. at this stage its not entirely clear what needs to be made, but buildbot is more geared towards automating builds, not manually triggering them
18:35:27  <thealphanerd>++
18:35:53  <jbergstroem>Fishrock123: __but__, buildbot nine is pretty much one big api; hence my suggestion on creating the frontend we want
18:36:03  <Fishrock123>ah
18:36:07  <thealphanerd>I'd be interested to find out what travis is capable of... and especially if they could get us custom boxes to run it on
18:36:12  <jbergstroem>anyway, i don't want to talk too much about buildbot, rather show a proof of concept
18:36:16  <thealphanerd>the way they sand box is a++
18:36:20  <Fishrock123>I'm totally down for building the frontend of something like that
18:36:24  <jbergstroem>thealphanerd: if custom is _our_ hardware then i'll have it in mind
18:36:38  <Fishrock123>^
18:36:41  <thealphanerd>indeed
18:36:54  <jbergstroem>but still, having commercial interests in between of our own is itchy
18:37:01  <thealphanerd>at the very least I'm interested in moving citgm there if it is possible
18:37:08  <thealphanerd>I'd like citgm to be way more sand boxed than it is
18:37:32  <jbergstroem>thealphanerd: turning the question around: how would we improve our sandbox?
18:37:36  <jbergstroem>chroot?
18:37:48  <jbergstroem>limited internet access? paths?
18:37:54  <thealphanerd>specifically... I'd like to sand box changes
18:38:00  <jbergstroem>whats mean?
18:38:13  <thealphanerd>so any modifications to the system while the test is running are rolled back after the run
18:38:33  <jbergstroem>thats not really sandboxing though
18:38:42  <jbergstroem>thats more about state
18:38:44  <thealphanerd>what would be the appropriate term for that?
18:38:59  <jbergstroem>in filesystems you'd refer to snapshots
18:39:14  <thealphanerd>ahhh ok
18:39:27  <thealphanerd>so yeah... I'd love it if citgm could run off a snap shot, and roll back after
18:39:39  <jbergstroem>sandboxing (especially in security terms such as grsec, selinux or the sandbox binary) means you control what an application is allowed to do
18:40:04  <jbergstroem>that scares me a bit too, more so than being able to roll back snapshots
18:40:28  <jbergstroem>for instance; npm library $x decides to dump full ENV to stdout because it doens't debug its test suite enough
18:40:31  <jbergstroem>we be like "ouch"
18:41:26  <jbergstroem>thealphanerd: are you running the current queued build? ima like to restart jenkins
18:41:50  <thealphanerd>all done
18:41:53  <thealphanerd>on my end
18:41:56  <jbergstroem>too bad we apparently need to restart ever 3-4 days :(
18:42:01  <jbergstroem>checking job owner now
18:42:37  <jbergstroem>ok restarting
18:45:01  <thealphanerd>:D
19:00:38  * chorrelljoined
19:26:52  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
20:31:12  <jbergstroem>rvagg, orangemocha: ping?
20:31:17  <jbergstroem>(nothing from redfin btw)
20:31:52  <orangemocha>jbergtroem pong
20:32:04  <jbergstroem>sweet; lets see how we go. thanks for stsaying online :)
20:32:15  <orangemocha>mmm, but they didn't confirm?
20:32:16  <jbergstroem>*staying
20:32:47  <jbergstroem>well i suggested and they kind of picked a time. in hindsight i guess i could've been clearer by setting it in stone
20:35:04  <orangemocha>I hope I don't fall asleep during the meeting ;)
20:35:20  <jbergstroem>yeah likewise
20:35:25  <jbergstroem>too many timezones the last few days
20:43:46  <thealphanerd>meeting with redfin coming up'/
20:43:48  <thealphanerd>?
20:44:11  <jbergstroem>yes in 15 or perhaps not
20:44:17  <jbergstroem>but shortly, hopefully this week
20:44:27  <jbergstroem>if it doesn't fire today i'll make sure we get something this week
20:44:47  <thealphanerd>ok cool
20:44:54  <thealphanerd>I have a lead for travis I'm going to be following up on
20:44:56  <thealphanerd>fwiw
20:45:10  <thealphanerd>rumor has it that the majority of stuff they are testing right now is node
20:45:11  <jbergstroem>do it
20:45:22  <thealphanerd>so I think they have a vested interest in helping the project
20:45:24  <jbergstroem>The more options the better.
20:46:12  <thealphanerd>indeed
20:52:50  * Fishrock123quit (Remote host closed the connection)
21:04:26  * Fishrock123joined
21:19:09  * Fishrock123quit (Remote host closed the connection)
21:24:52  * Fishrock123joined
21:32:41  * Fishrock123quit (Remote host closed the connection)
21:39:18  * Fishrock123joined
21:40:57  * Fishrock123quit (Remote host closed the connection)
21:53:08  * Fishrock123joined
21:54:27  * jenkins-monitorquit (Remote host closed the connection)
21:54:37  * jenkins-monitorjoined
21:54:43  * jenkins-monitor1quit (Remote host closed the connection)
21:54:54  * jenkins-monitor1joined
22:04:47  <orangemocha>so no call?
22:29:10  * Fishrock123quit (Remote host closed the connection)
22:29:53  * jenkins-monitorquit (Remote host closed the connection)
22:30:04  * jenkins-monitorjoined
22:30:09  * jenkins-monitor1quit (Remote host closed the connection)
22:30:19  * jenkins-monitor1joined
23:04:38  * Fishrock123joined
23:16:49  * Fishrock123quit (Remote host closed the connection)
23:20:44  <rvagg>jbergstroem: doh! did the call go ahead? I failed to put it on my calendar so was oblivious until I just read the email
23:24:11  * Fishrock123joined
23:30:54  * Fishrock123quit (Remote host closed the connection)
23:46:06  * Fishrock123joined
23:46:16  * Fishrock123quit (Remote host closed the connection)