'lhci autorun' waits indefinitely at run #1 in gitlab runner CI #936
Unanswered
jjunyjjuny
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
hello. I want to run the nextjs project in gitlab runner and measure the performance, but it is no longer going on in 'run #1'.
'node:16 docker image' does not have chromium. So I'm installing it
any other essential libraries need like chromium? I'm guessing there's no library that Lighthouse essentially uses in a pure node environment(node:16 docker image)...
I tried using "cypress/browsers:node16.17.0-chrome106" docker image.
I was able to get away from waiting indefinitely in run #1. Instead, the error message "Runtime error encountered: The page provided is not HTML (served as MIME type )."
However, when requested with 'curl' (curl -v localhost:8080/order/history), text/html response came down normally..
Everything works fine in my local environment, but I'm not sure why it didn't work properly in the gitlab runner ci environment
I want to keep using "node:16" images
Beta Was this translation helpful? Give feedback.
All reactions