sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #20091
[Bug 1213977] Re: Sikuli 1.0.1 not reporting failure when originating from child script
Thanks I will check and revise.
** Summary changed:
- Sikuli 1.0.1 not reporting failure when originating from child script
+ [1.0.1] not reporting failure when originating from child script
** Changed in: sikuli
Status: New => In Progress
** Changed in: sikuli
Importance: Undecided => High
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.1.0
--
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:
[1.0.1] not reporting failure when originating from child script
Status in Sikuli:
In Progress
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
References