Eric Bidelman

Thanks for the link. I'll take a look. On Thu, Jun 29, 2017 at 12:42 PM Kim T wrote: > You can do it either way. But if you pre-build...

Cool thank you. I was on vacation and havent had the time to look into pushing this up to Docker, but will after I catch up on work stuff :)...

Hmm, it looks like something is up with CPU never being idle on WPT. That's causing TTI to Error out and never calculated. I wonder what version of Lighthouse they're...

Good call. Want to send a PR?

There's no guarantees on uptime, retention, or reports being available, long-term. I suggest [running your own setup ](https://github.com/ebidel/lighthouse-ci#running-your-own-ci-server) if that's something important to you :)

Can you clarify the question? On Mon, Feb 25, 2019, 7:12 AM Alexander Lichter wrote: > It is necessary except when you running your own API which has access to...

For that case, I'd just run the `lighthouse` CLI or NPM module against your local app. You could use ngrok to expose a local server...

Today, you should be able to take the container and run it in any env. But for the large CIs it would be nice to have configs/integrations. Can you point...

Thanks. You're right that the helper `runlighthouse.js` script is tied to Github and Travis. Would running your own Docker container that runs chrome + Lighthouse work for Bit bucket? https://github.com/ebidel/lighthouse-ci/tree/master/builder....

None from my side On Fri, Jun 1, 2018, 3:58 AM Gaurav Sangle wrote: > Any updates on this? > > — > You are receiving this because you commented....