Skip to content

Did lighthouse CI changed criteria after Jun 23? #1113

@aloxe

Description

@aloxe

I installed Lighthouse CI on my project workflow with a simple configuration It was using @lhci/cli@0.14.x and was triggered on every PR.

From 23 June, it started to report errors, not passing the PR. Reverting changes and versions did not solve the issue. In fact manually running he lighthouse CI on the exact same code base is now reporting errors. Some errors do not make sense with NaN scores.

   ✘  lcp-lazy-loaded failure for minScore assertion
       Largest Contentful Paint image was not lazily loaded
       https://web.dev/articles/lcp-lazy-loading
       Audit did not produce a value at all. "minScore" might not be a valid assertion for this audit.

        expected: >=0.9
           found: NaN
      all values: NaN

Last lighthouse CI with OK results

Same lighthouse CI on the same codebase with KO results

The codebase and the github utilities remained untouched between the two. So I am wondering if thiere was not a change on the lighthouse side that could have triggered this change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions