3 ms·
Not sure if it's just me, but the Lighthouse CLI is so buggy that I've resorted to setting to up to run in a docker container so that it doesn't crash when tryi
by hobbescotch 5y ago
Not sure if it's just me, but the Lighthouse CLI is so buggy that I've resorted to setting to up to run in a docker container so that it doesn't crash when trying to load certain sites/configurations. Hope that they work on improving stability at some point. That being said, kudos to the team on the release, I'm sure this is a challenging project to work on!
- disasterkitsltd 5y agoIronically I've found the CLI to be the only stable channel of Lighthouse. What do you see that docker fixes?
- hobbescotch 5y agoFixes this issue basically: https://github.com/GoogleChrome/lighthouse/issues/6512#:~:text=PROTOCOL_TIMEOUT%20refers%20to%20the%20situation,uses%20to%20talk%20to%20Chrome https://github.com/GoogleChrome/lighthouse/issues/6512#:~:te.... Tried all of the proposed solutions and this error still pops up on certain sites and certain configuration settings. Felt totally random when it started happening.
- InternalRun 5y agoI’ve experienced the same as you, I’ve lost many hours to fixing different protocol time out errors. We’re running it in ECS now and it’s pretty stable, every now and then one pops up but is fixed by retrying the job.
- hoten 5y agoDo you have a good record of these sites/configurations? We suspect it's related to the host environment in some way that we can't reproduce on our machines. It'd be useful information for debugging if you can share it. Thanks!