sikuli-driver team mailing list archive

Thread
Date

[Bug 597853] Re: A sikuli script's exit code doesn't correspond with script success

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: RaiMan <rmhdevelop@xxxxxx>
Date: Thu, 21 Feb 2013 12:46:35 -0000
Reply-to: Bug 597853 <597853@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: sikuli
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/597853

Title:
  A sikuli script's exit code doesn't correspond with script success

Status in Sikuli:
  Fix Released

Bug 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
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/597853/+subscriptions