I am unable to run my unit tests via the command line:
elm-test
PS C:\my_path\client> elm-test Downloading binaries from
https://dl.bintray.com/elmlang/elm-test/0.18.6/win32-x64.tar.gz
Compilation failed for
C:\my_path\client\elm-stuff\generated-code\elm-community\elm-test\src\Mainc5862d6
a0878fab784555034eda0ebc7.elm
Note:
I'm not sure if this is a bug on the package or if it's within my control.
Unluckily for you, you've got elm-test#0.18.6, which had a few bugs in it.
The latest version should fix the issue.
Related
I'm running Serverless 2.15.0 with Node 14.15.0. I've tried installing both with npm i -g and by using the curl script in the tutorial. I have Maven 3.6.3 installed
When I try to run a simple Java "hello world" function locally, I get this message:
Serverless: Building Java bridge, first invocation might take a bit longer.
Then Serverless just hangs. No error message, nothing. When I try to run with SLS_DEBUG=*, there are no messages after that point.
The only thing I've been able to Google is this, but there isn't any resolution to the problem. The other thing I've found is this but there seems to be no java directory where Serverless is installed, so I can't manually compile the pom file.
Anyone know how to fix this problem?
The problem is that they moved the path of the java runtime wrapper. Base paths differ regarding install location.
NVM (global installation)
cd ~/.nvm/versions/node/v16.13.1/lib/node_modules/serverless/lib/plugins/aws/invoke-local/runtime-wrappers/java
mvn package
NPM (global installation)
cd ~/.npm-global/lib/node_modules/serverless/lib/plugins/aws/invokeLocal/runtimeWrappers/java
mvn package
Homebrew
cd /usr/local/Cellar/serverless/2.29.0/libexec/lib/node_modules/serverless/lib/plugins/aws/invokeLocal/runtimeWrappers/java
mvn package
Replace 2.29.0 with installed serverless version.
suddenly the test I have in testcafe stop working.
I have try to reinstall again the teamcity reporter with:
npm install -g testcafe testcafe-reporter-teamcity
and
npm install testcafe testcafe-reporter-teamcity
I can see that I have the folder testcafe-reporter-teamcity in my node_modules. But for some reason it cant find it.
Still the error that I get when running my test in local with the command:
testcafe firefox tests -c 4 --skip-js-errors --reporter teamcity
It will return the error:
ERROR The provided "teamcity" reporter does not exist. Check that you have specified the report format correctly.
Found the issue.
Just downgrading the version to
"testcafe-reporter-teamcity": "1.0.10"
seems to work perfectly.. for some reason 1.0.11 is giving this issue.
The build is failing with:
"Error: Npm failed with return code: 9009"
When we look at, here's what we noticed:
Till date (where there were no issues), build used to run on nmp 6.9.0 and node v10.16.3
Since the build started failing, we noticed the versions got auto-upgraded to npm/6.12.0 node/v12.13.0.
Please advise how to revert back to older versions, or do if we need to see this issue in a different dimension?
You can use Nojd.js tool installer task to specify the version you want. Then set the Version Spec as below.
You will get the node/v10.16.3 and npm/6.9.0.
You should add this task before the npm task. If not, the default version of node.js and npm would be below.
If your project can build successfully in local, you can use self-hosted agent to build.
Hope this helps.
I get error PhantomJS does not exist at '/usr/local/phantomjs/bin/phantomjs on the terminal upon running the tests (npm tests) for Cloudboost Javascript SDK repo. Any idea how to fix this?
Install PhantomJS from here, and create a symlink of the downloaded folder in your /usr/local/ directory. Run the command npm test again and that error would be gone.
I have a Git pre-commit hook that runs a Grunt command. However, Grunt is not on the path that IDEA runs under, so when I try to commit through the IDE I get a grunt: command not found error.
How can I ensure that Grunt is available to IDEA?
Turns out that this is because /usr/local/bin wasn't on the PATH (in OSX). See https://stackoverflow.com/a/17557522/555642.
I also had the same issue and then I executed the npm install. Thereafter I was able to run the grunt commands. Tryout and see this might fix the issue.