sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

It should usually do that.

example:

main.sikuli
-- calls 
sub1.sikuli
-- which in turn calls
sub2.sikuli

sub2.sikuli produces an error and you get this feedback:
stop line in running script *** [error] script [ mainTest ] stopped with error in line 5
error message *** [error] FindFailed ( can not find 1376931487082.png on the screen. )
the trace back block +++ [error] --- Traceback --- error source first
line: module ( function ) statement 
here the error happened *** 4: sub2 ( sub2_1 ) find("1376931487082.png")
here the sub2 was called *** 7: sub ( sub_1 ) sub2_1("hello two")
[error] --- Traceback --- end --------------

the text before the *** are my comments.

Could you give me an example, whre the information is not sufficient?

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

Title:
  Sikuli 1.0.1 not reporting failure when originating from child script

Status in Sikuli:
  New

Bug description:
  starting in version 1.0, the log file that shows errors is not as
  detailed as version 903.

  Example....

  I have a main script that is calling another script...

  there is a failure in that other script but Sikuli 1.0 and 1.0.1 only
  states there is an error in line 329 which is just the line where i'm
  calling the other script.

  this main script has no problems in 903 so i want to figure out why it
  failed and I cant since there is no detail on where the child script
  is failing only that there is a failure in that child script.

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