This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Exit codes from scriptcs.exe are not propagated #67
Comments
paulbouwer
added a commit
to paulbouwer/svm
that referenced
this issue
Mar 30, 2015
paulbouwer
added a commit
that referenced
this issue
Mar 30, 2015
Issue #67 - Exit codes from scriptcs.exe are not propagated
Fixed in ebd9aec. It was only an issue in the c:\ > scriptcs a.csx
ERROR: Could not find file 'C:\a.csx'. - 'C:\a.csx'.
c:\ > echo %errorlevel%
1
c:\> scriptcs -v
_ _
___ ___ _ __(_)_ __ | |__ ___ ___
/ __|/ __| '__| | '_ \| __// __/ __|
\__ \ (__| | | | |_) | |_| (__\__ \
|___/\___|_| |_| .__/ \__\\___|___/
|_| Version: 0.14.0
c:\ > echo %errorlevel%
0 paul@ubuntu:~$ scriptcs a.csx
ERROR: Could not find file "/home/paul/a.csx". - '/home/paul/a.csx'.
paul@ubuntu:~$ echo $?
1
paul@ubuntu:~$ scriptcs -v
_ _
___ ___ _ __(_)_ __ | |__ ___ ___
/ __|/ __| '__| | '_ \| __// __/ __|
\__ \ (__| | | | |_) | |_| (__\__ \
|___/\___|_| |_| .__/ \__\\___|___/
|_| Version: 0.14.0
paul@ubuntu:~$ echo $?
0 |
👍 great work @paulbouwer I also retried my use case and 0.4.1 fixed it for me. |
That error message from scriptcs.exe is, er, interesting scriptcs/scriptcs#1010 |
Yes - it is ... confusing 😄 |
Should be fixed in 0.15 On 03:51, Fri, 3 Apr 2015 Paul Bouwer notifications@github.com wrote:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems as though svm always returns a zero exit code, even if scriptcs.exe returns something else.
This tripped me up to today whilst writing a script pack test automation app.
The text was updated successfully, but these errors were encountered: