SikuliX

[2.0.4] run from commandline: -f does not work as expected

Asked by Melaku Bartolomeos

When running a test in Sikulix 2.0.4 from command line with -d 3 -f arguments, I am not getting all output I see in Message section of SikuliX IDE.

The same arguments in SikuliX 1.1.2 give what I expect and match what is posted the Message Pane of IDE.

Any idea what I need to do to get this output that I see in IDE in commandline?

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said : 		#1

what kind of messages are you missing?

Please paste small part of the message area and the respective part of the logfile.

Revision history for this message
Melaku Bartolomeos (bartolom) said : 		#2

In this example, I simulated a test failure and message area of IDE shows this: This is what I want to appear on console when running test in commandline. In Sikuli 1.1.2 I get this on console, but not in 2.0.4.

Running tests...
----------------------------------------------------------------------
E
======================================================================
ERROR [9.125s]: test_2D_FileOpen_100pagesPDF (__main__.TcVis_File_Types)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "D:\TcVis_2D_FileOpen_100pagesPDF.sikuli\TcVis_2D_FileOpen_100pagesPDF.py", line 27, in test_2D_FileOpen_100pagesPDF
    click(stop)
UnboundLocalError: local variable 'stop' referenced before assignment

----------------------------------------------------------------------
Ran 1 test in 9.140s

FAILED (errors=1)

Generating XML reports...

Revision history for this message
RaiMan (raimund-hocke) said : 		#3

So we are not talking about plain Sikuli Scripts, but the usage of module unitest or similar.

If you want the complete message output into a file, then you can alternatively use > on commandline.

It might be, that the -f parameter has an implementation problem in 2.0.x

Revision history for this message
Melaku Bartolomeos (bartolom) said : 		#4

Thanks for looking into this.

Can you help with this problem?

Provide an answer of your own, or ask Melaku Bartolomeos for more information if necessary.

To post a message you must log in.