sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

** Summary changed:

- X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t
+ X-1.0rc2 Unittests not working with some scriptnames when called via command line with -t --- possible workaround

** Description changed:

+ --- possible workaround
+ 
+ script names starting with the letters c or m seem to work.
+ 
+ -----------------------------------------------------------
+ 
  This Bug was reproducable with the combinations WinXP & rc2 as well as
  with Win7 & rc3.
  
  When executing a Sikuli-test via commandline like
  
  sikuli-ide.bat -t <test.sikuli>
  
  sikuli has some odd behavior: The script does in some cases not load at
  all but only prints [error] null, and in other cases refuses to find any
  kind of image on the screen, resolving in FindFailed-Exceptions.
  
  A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
- All scripts where executed as 
+ All scripts where executed as
  
- Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script. 
+ Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
  Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
- Filenames f.sikuli and x.sikuli did nothing but printing [error] null 
+ Filenames f.sikuli and x.sikuli did nothing but printing [error] null
  
  I did not test more filenames yet.
  
  Look here for all the detail
  https://answers.launchpad.net/sikuli/+question/167514 (last posts)

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

Title:
  X-1.0rc2 Unittests not working with some scriptnames when called via
  command line with -t --- possible workaround

Status in Sikuli:
  New

Bug description:
  --- possible workaround

  script names starting with the letters c or m seem to work.

  -----------------------------------------------------------

  This Bug was reproducable with the combinations WinXP & rc2 as well as
  with Win7 & rc3.

  When executing a Sikuli-test via commandline like

  sikuli-ide.bat -t <test.sikuli>

  sikuli has some odd behavior: The script does in some cases not load
  at all but only prints [error] null, and in other cases refuses to
  find any kind of image on the screen, resolving in FindFailed-
  Exceptions.

  A quick test revealed the following correlation between name of the sikuli-script and the mentioned behavior:
  All scripts where executed as

  Filenames a.sikuli as well as b.sikuli resolved in a Find Failed Exception for every find() in the script.
  Filenames c.sikuli, d.sikuli, e.sikuli and m.sikuli worked normal.
  Filenames f.sikuli and x.sikuli did nothing but printing [error] null

  I did not test more filenames yet.

  Look here for all the detail
  https://answers.launchpad.net/sikuli/+question/167514 (last posts)

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