Unable to run in bash shell
See original GitHub issueOutput gets formatted with \ resulting in trying to write to a directory not supported by non-CMD terminals. Additionally, running without /p:CoverletOutputDirecotory
results in Project file does not exist
error.
Not sure how to work around this, or if it’s possible given that this value is hardcoded.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Can't run Bash script
To run the script you can specify full pathname as tikend's answer. If you want to use it as a command from any...
Read more >Unable to run shell script in terminal
Try this $ cd /path/to/script && ./myscript.sh. If it doesn't work run this command as superuser.
Read more >Unable to run shell script in windows 10 with Bash on Ubuntu
1 Answer 1 · This script is compiled in such a way that matters where it is running. · Another possible problem -...
Read more >Bash script won't run
I'm trying to run a bash script named 'serverloadtest.sh' to test a server is performing correctly. However, when I type serverloadtest.sh ...
Read more >Unable to run bash scripts on a windows installed runner
When trying to run a bash script against a windows runner, all the path separators are missing. Presumably the runner is sending backslashes ......
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
@paulers I was running into a similar issue going from git bash shell to my jenkins running linux and dotnet core. I ended up creating a MSBuild Response file (msbuild.rsp) and referencing that in the command line. It’s a new line separated file where you can define arguments you want msbuild to use. This is what I have in mine (named coverage.rsp)
Then the command-line or your bash script would will now look like this:
Git bash replaces forward with backward slashes a bit indiscriminately. See https://github.com/yarnpkg/yarn/issues/2785 . I have like a hundred dollar bounty on this issue if anyone’s bored.