Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Lighthouse failed to run performance audits for "/", adding back to queue." , in order to find the cause of the problem #213

Open
OSnuszka opened this issue Apr 25, 2024 · 4 comments

Comments

@OSnuszka
Copy link

OSnuszka commented Apr 25, 2024

Details

I use Unlighthouse to scan production domains, and some of them are not scannable due to this error appearing in the logs.
This error is looping during execution:
"Lighthouse failed to run performance audits for "/", adding back to queue."

I'm using unlighthouse-ci to execute my audits.
Below my configuration:

/// <reference types="unlighthouse" />
export default ({
  puppeteerClusterOptions: {
    chrome: {
      useSystem: false
    },
    maxConcurrency: 1,
  },
  
  puppeteerOptions: {
    headless: true,
    args: ["--no-sandbox"],
    },
  server: {
    open: true,
  },

  site: "some url here",
  scanner: {
    device: "desktop",
    skipJavascript: false,
    robotsTxt: false,
    sitemap: false,
    crawler: false,
    samples: 10,
    setTimeout: 60000,
    
  },
  debug: false,
  
});

@harlan-zw
Copy link
Owner

The error occurs from the lighthouse binary. Lighthouse itself does not expose any information on why it failed so not too sure what the solution is.

You can try and earlier version of Unlighouse which used a lighthouse version that didn't throw this issue as often.

@Dale-777
Copy link

Dale-777 commented May 1, 2024

is setTimeout an option for Scanner?

@OSnuszka
Copy link
Author

is setTimeout an option for Scanner?

to be honest, I noticed this timeout not work as expected, but I keep that in configuration anyway (It was a try to fix problem described in this ticket)

@raphaelbernhart
Copy link

Is there any update on this issue? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants