| 2010-06-23 21:02:41 |
Will P |
bug |
|
|
added bug |
| 2010-07-26 15:28:56 |
Will P |
description |
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script fails, raises an exception, or exits with "exit(1)"/"sys.exit(1)", the script will print out, "[sikuli] Exited with code 1", but then the actual return value of the script is 0. (I'm checking the error code with, "echo $?" right after executing the script). So this makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8 |
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script exits with a non-zero exit code (e.g., the test fails or raises an exception), the script prints out, "[sikuli] Exited with code 1", but then actually returns 0.
You can check the return value by calling "echo $?" right after executing the script.
It's only a minor annoyance, but it makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8 |
|
| 2010-07-26 15:29:29 |
Will P |
description |
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script exits with a non-zero exit code (e.g., the test fails or raises an exception), the script prints out, "[sikuli] Exited with code 1", but then actually returns 0.
You can check the return value by calling "echo $?" right after executing the script.
It's only a minor annoyance, but it makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8 |
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script exits with a non-zero exit code (e.g., the test fails or raises an exception), the script prints out, "[sikuli] Exited with code 1", but then actually returns 0.
You can check the return value by calling "echo $?" right after executing the script.
I have a workaround, so this is only a minor annoyance for me. It makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8
|
|
| 2010-07-26 15:29:55 |
Will P |
description |
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script exits with a non-zero exit code (e.g., the test fails or raises an exception), the script prints out, "[sikuli] Exited with code 1", but then actually returns 0.
You can check the return value by calling "echo $?" right after executing the script.
I have a workaround, so this is only a minor annoyance for me. It makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8
|
I am running sikuli scripts from the command line: "Sikuli-IDE.app/sikuli-script.sh -r my-script.sikuli". If a Sikuli script exits with a non-zero exit code (e.g., the test fails or raises an exception), the script prints out, "[sikuli] Exited with code 1", but then actually returns 0.
You can check the return value by calling "echo $?" right after executing the script.
I have a workaround, so this is only a minor annoyance for me currently. It makes it a little more difficult to test whether a script has succeeded, if the script is being called by other tools.
Using Sikuli 0.10.1 (downloaded 5/23/2010) on Mac 10.5.8
|
|
| 2010-07-29 03:51:54 |
Tsung-Hsiang Chang |
sikuli: status |
New |
Fix Committed |
|
| 2013-02-21 12:46:35 |
RaiMan |
sikuli: status |
Fix Committed |
Fix Released |
|
