00:29:43  * rmgjoined
00:32:56  * rmg_quit (Ping timeout: 256 seconds)
02:35:31  <Trott>indutny: You probably know this already but just in case: If no one responds here, you can open an issue in https://github.com/nodejs/build. You can model your issue on https://github.com/nodejs/build/issues/597.
07:40:13  * rmg_joined
07:43:34  * rmgquit (Ping timeout: 264 seconds)
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:40  * mylesborinsjoined
11:08:51  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
13:10:33  * node-ghjoined
13:10:33  * node-ghpart
13:10:34  <indutny>here it goes https://github.com/nodejs/build/issues/671
13:10:42  * node-ghjoined
13:10:43  * node-ghpart
13:30:17  * node-ghjoined
13:30:17  * node-ghpart
14:01:59  * node-ghjoined
14:02:00  * node-ghpart
14:51:21  * node-ghjoined
14:51:22  * node-ghpart
14:51:39  * node-ghjoined
14:51:39  * node-ghpart
14:52:16  * node-ghjoined
14:52:17  * node-ghpart
14:55:12  * node-ghjoined
14:55:12  * node-ghpart
15:02:31  * node-ghjoined
15:02:31  * node-ghpart
15:32:31  * not-an-aardvarkjoined
19:13:13  * chorrelljoined
19:24:14  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:31:53  * refackjoined
21:35:42  <refack>Hi guy, I have a task idea; implement a mechanism like gclient or node-pre-gyp that will cache the deps artifacts for a faster build
21:36:01  <refack>At the moment for example Travis dies after 50minutes
21:41:32  <refack>Do you recon it's a `build` task or a `node` task?
21:43:22  * refackquit
21:43:30  * refackjoined
21:43:30  * refackquit (Client Quit)
21:46:41  * refackjoined
21:48:53  <ljharb>refack: you can certainly just cache things across travis builds
21:48:58  <ljharb>that's just some travis.yml entries
21:49:24  <ljharb>but if you rely on caching to make builds *pass* (instead of just using it to make them fast) then if the cache is ever busted, you'll be kind of screwed
23:23:20  <refack>If in busted you mean tampered, the chromium depot-tools use a mechanism to verify binaries with hashes, to protect against tampering
23:23:50  <refack>If by busted you meen cache-miss, then that's just a cache
23:24:51  <refack>I'm not talking just about travis, that's an example (that Travis is useless for us), the build is very long, and here on windows it's over delicate to rebuilds
23:25:42  <refack>Also for CI/CD (Deployment) we could always have a flag for `ignore cache`
23:26:23  <refack>INHO a build after a small change should not take longer then 5 minutes
23:29:43  * node-ghjoined
23:29:43  * node-ghpart
23:36:20  * node-ghjoined
23:36:20  * node-ghpart
23:36:35  * node-ghjoined
23:36:35  * node-ghpart