Appveyor CI failing
See original GitHub issueseems to be an issue with the \n
in ..\\node...
interpreted as newline
see https://ci.appveyor.com/project/fable-compiler/ts2fable/build/0.6.1-build.348#L408
warning Error running install script for optional dependency: "C:\\projects\\ts2fable\
ode_modules\\v8-profiler: Command failed.
Exit code: 1
Command: C:\\Windows\\system32\\cmd.exe
Arguments: /d /s /c node-pre-gyp install --fallback-to-build
Directory: C:\\projects\\ts2fable\
ode_modules\\v8-profiler
Output:
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
[CI] AppVeyor build fails inexplicably · Issue #67
Brief Description AppVeyor builds are failing completely due to a missing path. Version Current latest commit. Environment Looks like we're ...
Read more >Appveyor build fails whereas local build succeeds
The appveyor build for the project https://ci.appveyor.com/project/LogoFX/samples-specifications fails whereas the local build is just fine.
Read more >Appveyor tests failing during Github commits
Appveyor tests are failing when a PR is committed in Githib. In the traceback it indicates there's a checksum error when downloading a ......
Read more >Compile errors does not fail the job
It seems that failing to build a binary does not fail the job as show in https://ci.appveyor.com/project/obiltschnig/poco/build/build%20data...
Read more >Successful builds failing with code 259
Successful builds failing with code 259. This discussion is ... An invocation of bash src/ci/run.sh is then unblocked as the CI run script...
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 Free
Top 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
Feel free to do it @MangelMaxime
Yepp, i draw wrong conclusion from the output. Above lines are not from last CI build. The errror from the last build is