GitHub Community
Npm test never stops executing #25250
-
|
I used Added GitHub actions config for node.js: The code never passes the What am I doing wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
|
It seems that when you execute the command npm test , you should explicitly set the environment variable CI , no matter its value is true or false. You can try the below 2 methods to set this environment variable:
We can define it on workflow level, job level or step level, so that it can be available for different scopes. |
Beta Was this translation helpful? Give feedback.
-
|
Do you need both? CI=true npm test works but just setting the env var hangs when you add another command after the npm test
When just using env and I run -run: env I don’t see the CI var |
Beta Was this translation helpful? Give feedback.
-
|
when my workflow runs i have everything setup as you said but though it takes forever to run test on local it works fine but on github it takes forever |
Beta Was this translation helpful? Give feedback.
-
|
For anybody still reading this. |
Beta Was this translation helpful? Give feedback.
-
|
[If you are still reading this article]
Problem was related to the missing chromium package on ubuntu runner. After installing the chromium and exporting the environment variable, test has started running. |
Beta Was this translation helpful? Give feedback.
-
|
Run sudo apt install chromium-browser WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists… Building dependency tree… Reading state information… E: Unable to locate package chromium-browser Error: Process completed with exit code 100. cannot find chromium could you please help ? |
Beta Was this translation helpful? Give feedback.
-
|
'--exit' option works for me |
Beta Was this translation helpful? Give feedback.
-
|
I have no fucking idea how the fuck to install pycharm on my Chromebook
I've been trying to install it for five days and I've already been driven
crazy by so many beggar commands I've entered. The furthest I've gotten it
says this page or site is available in the Linux terminal. and that pure
fucking letters and doodles. This mother is harder to penetrate than a
Swiss bank vault.
El sáb, 8 de oct. de 2022 22:51, rupinder02 ***@***.***>
escribió:
… '--exit' option works for me
—
Reply to this email directly, view it on GitHub
<#25250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3KRSHGXS4AU7HOZQQUCDNLWCJMOHANCNFSM6AAAAAARARRFRU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
This one worked for me. "scripts": { |
Beta Was this translation helpful? Give feedback.
It seems that when you execute the command npm test , you should explicitly set the environment variable CI , no matter its value is true or false.
You can try the below 2 methods to set this environment variable:
Set CI directly in the command line, for example on Linux, macOS (Bash).
CI=true npm test
Define CI as an environment variable in the workflow.
env:
CI: true
We can define it on workflow level, job level or step level, so that it can be available for different scopes.