sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

well, understood.

... but following these 2 lines, there should be a block like

[error] --- Traceback --- error source first
line: module ( function ) statement
XXX:  ---module name--- (SlipsExpandedFunctionalityComplete.ts_expanded_functions) --- failing statement ---
[error] --- Traceback --- end --------------

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