A recent dependency upgrade merged into GoogleChrome/lighthouse-ci (which prompted minor-version bumps, not a major version bump) is causing lighthouse to fail to connect to the browser.
Error from our GitHub Actions output
```
Search logs
Run treosh/lighthouse-ci-action@v3
Action config
Collecting
Running Lighthouse 3 time(s) on ****
Run #1...failed!
Error: Lighthouse failed with exit code 1
at ChildProcess. (/home/runner/work/_actions/treosh/lighthouse-ci-action/v3/node_modules/@lhci/cli/src/collect/node-runner.js:103:21)
at ChildProcess.emit (events.js:314:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
Tue, 21 Feb 2023 16:06:49 GMT ChromeLauncher Waiting for browser.
Tue, 21 Feb 2023 16:06:49 GMT ChromeLauncher Waiting for browser...
Tue, 21 Feb 2023 16:06:49 GMT ChromeLauncher Waiting for browser.....
Tue, 21 Feb 2023 16:06:50 GMT ChromeLauncher Waiting for browser.......
Tue, 21 Feb 2023 16:06:50 GMT ChromeLauncher Waiting for browser.........
Tue, 21 Feb 2023 16:06:51 GMT ChromeLauncher Waiting for browser...........
Tue, 21 Feb 2023 16:06:51 GMT ChromeLauncher Waiting for browser.............
Tue, 21 Feb 2023 16:06:52 GMT ChromeLauncher Waiting for browser...............
Tue, 21 Feb 2023 16:06:52 GMT ChromeLauncher Waiting for browser.................
Tue, 21 Feb 2023 16:06:53 GMT ChromeLauncher Waiting for browser...................
Tue, 21 Feb 2023 16:06:53 GMT ChromeLauncher Waiting for browser.....................
Tue, 21 Feb 2023 16:06:54 GMT ChromeLauncher Waiting for browser.......................
Tue, 21 Feb 2023 16:06:54 GMT ChromeLauncher Waiting for browser.........................
Tue, 21 Feb 2023 16:06:55 GMT ChromeLauncher Waiting for browser...........................
Tue, 21 Feb 2023 16:06:55 GMT ChromeLauncher Waiting for browser.............................
Tue, 21 Feb 2023 16:06:56 GMT ChromeLauncher Waiting for browser...............................
Tue, 21 Feb 2023 16:06:56 GMT ChromeLauncher Waiting for browser.................................
Tue, 21 Feb 2023 16:06:57 GMT ChromeLauncher Waiting for browser...................................
Tue, 21 Feb 2023 16:06:57 GMT ChromeLauncher Waiting for browser.....................................
Tue, 21 Feb 2023 16:06:58 GMT ChromeLauncher Waiting for browser.......................................
Tue, 21 Feb 2023 16:06:58 GMT ChromeLauncher Waiting for browser.........................................
Tue, 21 Feb 2023 16:06:59 GMT ChromeLauncher Waiting for browser...........................................
Tue, 21 Feb 2023 16:06:59 GMT ChromeLauncher Waiting for browser.............................................
Tue, 21 Feb 2023 16:07:00 GMT ChromeLauncher Waiting for browser...............................................
Tue, 21 Feb 2023 16:07:01 GMT ChromeLauncher Waiting for browser.................................................
Tue, 21 Feb 2023 16:07:01 GMT ChromeLauncher Waiting for browser...................................................
Tue, 21 Feb 2023 16:07:02 GMT ChromeLauncher Waiting for browser.....................................................
Tue, 21 Feb 2023 16:07:02 GMT ChromeLauncher Waiting for browser.......................................................
Tue, 21 Feb 2023 16:07:03 GMT ChromeLauncher Waiting for browser.........................................................
Tue, 21 Feb 2023 16:07:03 GMT ChromeLauncher Waiting for browser...........................................................
Tue, 21 Feb 2023 16:07:04 GMT ChromeLauncher Waiting for browser.............................................................
Tue, 21 Feb 2023 16:07:04 GMT ChromeLauncher Waiting for browser...............................................................
Tue, 21 Feb 2023 16:07:05 GMT ChromeLauncher Waiting for browser.................................................................
Tue, 21 Feb 2023 16:07:05 GMT ChromeLauncher Waiting for browser...................................................................
Tue, 21 Feb 2023 16:07:06 GMT ChromeLauncher Waiting for browser.....................................................................
Tue, 21 Feb 2023 16:07:06 GMT ChromeLauncher Waiting for browser.......................................................................
Tue, 21 Feb 2023 16:07:07 GMT ChromeLauncher Waiting for browser.........................................................................
Tue, 21 Feb 2023 16:07:07 GMT ChromeLauncher Waiting for browser...........................................................................
Tue, 21 Feb 2023 16:07:08 GMT ChromeLauncher Waiting for browser.............................................................................
Tue, 21 Feb 2023 16:07:08 GMT ChromeLauncher Waiting for browser...............................................................................
Tue, 21 Feb 2023 16:07:09 GMT ChromeLauncher Waiting for browser.................................................................................
Tue, 21 Feb 2023 16:07:09 GMT ChromeLauncher Waiting for browser...................................................................................
Tue, 21 Feb 2023 16:07:10 GMT ChromeLauncher Waiting for browser.....................................................................................
Tue, 21 Feb 2023 16:07:10 GMT ChromeLauncher Waiting for browser.......................................................................................
Tue, 21 Feb 2023 16:07:11 GMT ChromeLauncher Waiting for browser.........................................................................................
Tue, 21 Feb 2023 16:07:11 GMT ChromeLauncher Waiting for browser...........................................................................................
Tue, 21 Feb 2023 16:07:12 GMT ChromeLauncher Waiting for browser.............................................................................................
Tue, 21 Feb 2023 16:07:12 GMT ChromeLauncher Waiting for browser...............................................................................................
Tue, 21 Feb 2023 16:07:13 GMT ChromeLauncher Waiting for browser.................................................................................................
Tue, 21 Feb 2023 16:07:13 GMT ChromeLauncher Waiting for browser...................................................................................................
Tue, 21 Feb 2023 16:07:14 GMT ChromeLauncher Waiting for browser.....................................................................................................
Tue, 21 Feb 2023 16:07:14 GMT ChromeLauncher Waiting for browser.......................................................................................................
Tue, 21 Feb 2023 16:07:14 GMT ChromeLauncher:error connect ECONNREFUSED ::1:39445
Tue, 21 Feb 2023 16:07:14 GMT ChromeLauncher:error Logging contents of /tmp/lighthouse.Qa1gTSz/chrome-err.log
Tue, 21 Feb 2023 16:07:14 GMT ChromeLauncher:error
DevTools listening on ws://127.0.0.1:39445/devtools/browser/fafde2c9-a630-42a8-b08d-b28ec3977acd
[0221/160649.802893:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[0221/160649.836238:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
Unable to connect to Chrome
Error: LHCI 'collect' has encountered a problem.
```
Hoping that pinning to 0.9.0 will alleviate the failures we're now seeing, and if my team can gain some time we could potentially dedicate to a proper remediation, we'd be happy to try to resolve further if it isn't already addressed by that point.
Just realizing that I ran this in the browser, and it didn't cause the yarn.lock to update. I'll pull this down, install, and push up a commit with updates to yarn.lock. Sorry for the un-tidy PR process!
A recent dependency upgrade merged into GoogleChrome/lighthouse-ci (which prompted minor-version bumps, not a major version bump) is causing lighthouse to fail to connect to the browser.
Error from our GitHub Actions output
``` Search logs Run treosh/lighthouse-ci-action@v3 Action config Collecting Running Lighthouse 3 time(s) on **** Run #1...failed! Error: Lighthouse failed with exit code 1 at ChildProcess.Hoping that pinning to 0.9.0 will alleviate the failures we're now seeing, and if my team can gain some time we could potentially dedicate to a proper remediation, we'd be happy to try to resolve further if it isn't already addressed by that point.