Lighthouse could not test page - LHError: PROTOCOL_TIMEOUT

Open
#108 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Start with index.js lines 36-68, then compare the documented --lighthouse.config and --lighthouse.flags options with the Chrome flags configured there. Reproduce the PROTOCOL_TIMEOUT against the localhost page and determine whether an additional flag can be passed; done means the supported configuration path is documented or the issue is narrowed to an upstream Lighthouse failure.

Written by the indexing model from the issue text.

Description

Your question

Hi
I'm trying to test pages with sitespeedio/sitespeed.io:25.11.0-plus1
But receiving the error:
ERROR: Lighthouse could not test http://localhost:3000/testPage please create an upstream issue: https://github.com/GoogleChrome/lighthouse/issues/new?assignees=&labels=bug&template=bug-report.yml LHError: PROTOCOL_TIMEOUT
at /lighthouse/node_modules/lighthouse/lighthouse-core/gather/driver.js:348:50.....

After researching, one possible solution that could help is to add a chrome flag "--disable-dev-shm-usage" (https://github.com/GoogleChrome/lighthouse/issues/6512)
But none of the options for passing flags to the lighthouse plugin, as I see it, does not work for me (from --lighthouse.config config.js or --lighthouse.flags flag.json)
And as I see here https://github.com/sitespeedio/plugin-lighthouse/blob/main/index.js#L36-L68 the chrome flags are already set but without the ability to pass additional flags into it (maybe I'm wrong).
@soulgalore could you please tell me if there are any other ways to pass chrome flags to the lighthouse plugin?
Or maybe there are other ways to fix the error?

Dominant language
JavaScript
Stars
31
Forks
21
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sitespeedio/plugin-lighthouse

All issues in sitespeedio/plugin-lighthouse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.