sikuli-driver team mailing list archive

[RaiMan <question251939@xxxxxxxxxxxxxxxxxxxxx>]

Question #251939 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/251939

RaiMan requested more information:
ok, then you seem to know what you are doing ;-)

What version of Sikuli are you using?

Are you using the modified runner (takes screenshots on failures)?

Since the problem happened after you added the tests: Is the original version (without the new tests) still working?
If yes, are there any new features you are using, that you never used before in the other tests?

Do all tests need to be in one script? (the script might be too big -
there is a restriction of 64KB from Java/Jython)? Why not divide it into
modules, that are imported and run by a main file (which adds some
options for more flexibility)

MemoryLeaks: different versions of Sikuli had different cases of memory leaks.
These should be fixed with 1.0.1+

But I have to admit, that from time to time someone complains about
random crashes/hangs of long running scripts. But till now, these cases
where rather seldom and finally accepted as risk but without any
solution.

So the only way to get a result is, to go back to a running situation
and add new things step by step until it does not work anymore.

What I do not understand: If you are producing different report files
for different test suits in your run: How can it be that you do not get
any reporting?

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.