Didn't work in CICD
See original GitHub issueFAQ
- Yes, my issue is not about variability or throttling.
- Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
URL
https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7951614
What happened?
I run it correctly locally, but when I run gitlab ci, I get an error。The error message is as follows:
(node:100) UnhandledPromiseRejectionWarning: Error
at new LauncherError (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/utils.js:26:22)
at new ChromePathNotSetError (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/utils.js:33:9)
at Object.linux (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-finder.js:128:15)
at Function.getFirstInstallation (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:126:51)
at Launcher.launch (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:185:43)
at Object.launch (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:37:20)
at /builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/build/performance/lighthouse.js:46:39
at Object.<anonymous> (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/build/performance/lighthouse.js:108:3)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
What did you expect?
run collectly with gitlab ci, I want to run performance when deploy pages
What have you tried?
nothing
How were you running Lighthouse?
CLI
Lighthouse Version
9.6.1
Chrome Version
No response
Node Version
14.17.3
OS
Mac
Relevant log output
(node:100) UnhandledPromiseRejectionWarning: Error
at new LauncherError (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/utils.js:26:22)
at new ChromePathNotSetError (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/utils.js:33:9)
at Object.linux (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-finder.js:128:15)
at Function.getFirstInstallation (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:126:51)
at Launcher.launch (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:185:43)
at Object.launch (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/node_modules/chrome-launcher/dist/chrome-launcher.js:37:20)
at /builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/build/performance/lighthouse.js:46:39
at Object.<anonymous> (/builds/FoU-rNW-/0/appstore-frontend/appstore-mobile/build/performance/lighthouse.js:108:3)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Troubleshooting CI/CD - GitLab Docs
Common CI/CD issues · Jobs or pipelines don't run when expected · Pipeline with many jobs fails to start · A job runs...
Read more >Troubleshoot CI-CD, Azure DevOps, and GitHub issues
Use different methods to troubleshoot CI-CD issues in Azure Data Factory and Synapse Analytics.
Read more >Azure DevOPS CI/CD Trigger not working stopped suddenly
Try to clone the build and release pipeline, set CI/CD to check if it works. If the issue persists, please capture screenshots for...
Read more >Changing your CI tool won't fix your broken pipelines
May 11, 2018 · 9 minute read · Tags: ci/cd , devops ... You can't blame your CI tool if you didn't provide...
Read more >Azure DevOps CI/CD pipeline No package found error
@GeralexGR I tried it, but it didn't work, got slightly different error message: Error: No package found with specified pattern: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7951614 isn’t working for me, do you have another URL?
I added a chrome image to docker, and new problems occurred after running
(node:91) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:42697 [318](https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7969622#L318) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) [319](https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7969622#L319)(Use
node --trace-warnings …to show where the warning was created) [320](https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7969622#L320)(node:91) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
–unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) [321](https://git.n.xiaomi.com/appstore-frontend/appstore-mobile/-/jobs/7969622#L321)(node:91) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
There was no problem with mirroring, it was later solved by adding --no-sandboxconst chrome = await chromeLauncher.launch({ chromeFlags: ['--headless', '--no-sandbox'], });
Thank you so much and good luck~