Patrick Hulce

Thanks for filing @ardevelop! Lighthouse CI already retries each Lighthouse run up to 3 times internally when it encounters PROTOCOL_TIMEOUT and other related failure types, so if we finally surfaced...

> however, this is not occasional as the problem is completely repeatable programatically Please file an issue in Lighthouse with the *exact* repro steps if this is repeatable. Thus far,...

The [lighthouse core docs describe minimum recommendations](https://github.com/GoogleChrome/lighthouse/blob/master/docs/variability.md#run-on-adequate-hardware). If you do end up finding truly reproducible steps that would be awesome :)

Thanks for sharing those steps @dimension85 I really appreciate the effort you gone to helping find a repro here ! Those logs are indicating that Chrome is *crashing* in the...

Thanks for filing @koh110! We're not concerned enough about this vulnerability (low severity, requires an attacker to already be able to write `.ini` files to sensitive directories) to justify completely...

Hm that's very strange @royletron thanks for filing!! There shouldn't be anything Node 12 specific here (it's just the minimum), and using node 14 was not enough for me to...

Please fill out the entirety of [an issue template](https://github.com/GoogleChrome/lighthouse-ci/tree/main/.github/ISSUE_TEMPLATE) with reproduction steps for us to be able to help. Also see https://github.com/GoogleChrome/lighthouse-ci/issues/258 which has already discussed this exact error message...

Thanks for filing @patriciamarchand! There is no such parameter, but we can let this issue track building one :)

> Why is the lighthouse report viewer not included in the lighthouse report server? The code for the viewer is in the upstream Lighthouse core repo and not easily hosted...

> Are you using this data to generate the diff report? Yes > For the Lighthouse report viewer whitch data are you using? The same JSON data. > I did...