[request] Find failed: more features for debugging
Bug #1204634 reported by
Erick Quinteros
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
In Progress
|
Medium
|
RaiMan |
Bug Description
Version: Sikuly finally 1.0.0
OS: Windows 7 64-bits
Reproduce: Execute find operations for a long period of time.
When I use the find operation (or others than use find inside) on a automatized scenario during long periods of time, the find operation fail in some point, if I try to find the image again is found but in a long execution it fails, and not always the same image fail.
summary: |
- Find fail after use it 30 minutes or more + Find fail after use it for a long time |
Changed in sikuli: | |
milestone: | 1.1.0 → 1.2.0 |
summary: |
- [1.0] Find fail after use it for a long time + [request] Find failed: more features for debugging |
Changed in sikuli: | |
milestone: | 2.0.0 → 2.1.0 |
To post a comment you must log in.
FindFailed exceptions are only raised/thrown, if a (explicit or implicit) search (explicit or implicit) for an image on the screen is not successful within the given wait time (in the standard 3 seconds).
In long running situations, there might be other system aspects that eventually lead to a delay of the GUI actions and hence to a FindFailed. This can only be debugged, if you take care, that a screenshot of the FindFailed situation is available afterwards (e.g. the latest screen image used to search).
Currently, there is no compact feature in Sikuli to support such a tracking. You must setup your own function and use it instead of all (or at least the critical ones).
Another option is to replace all find operations with wait(image, maxtime)
e.g. instead of
click(some_image)
use some_image, 20))
click(wait(
which does not do any harm, since it will come back in the moment the some_image appears, but add some robustness for situations, where the image's appearance is delayed for a reason you cannot foresee in your script.