I have one computer using itest that can open and run a python session, however, on another device with the same itest version it manages to find the python.exe but shortly after loading just says...
disconnected...
with no usable information. What could be different on these two devices to cause 2 different outcomes? Is there a option or license that needs to be enabled in order to run/open a python session? (even fails when starting directly off the session)
Resolved. Apparently our Proxy was blocking it. I guess this uses some kind of post/get request to run python for some reason and our proxy blocked this?
No special license is required to run the Python session. You can set the Python interpreter that you want iTest to use under: Window / Preferences / Spirent / Python Interpreter
Is there any other error returned in the response or does it just look like this:
Spirent Communications Python command interpreter. Copyright (c) 2005 - 2019, Spirent Communications. Disconnected...
Severity Message Index Step Procedure Session Source File
Error Error attempting to open connection to server: Openning Python connection failed: cause: Failed to recive suitable Hello response from pydevconsole. Last msg received: PythonInterpreterError: HTTP server returned unexpected status: Service UnavailableCommand Line used: (unable to determine command line) 9.1 1 pyrunme s1 terminal ProbeSanityTest.fftc
The user has access to the python.exe file and can also run it manually.
Its being called from a open calling a python session which links to the .exe
Severity Message Index Step Procedure Session Source File
Error Error attempting to open connection to server: Openning Python connection failed: cause: Failed to recive suitable Hello response from pydevconsole. Last msg received: PythonInterpreterError: HTTP server returned unexpected status: Service UnavailableCommand Line used: (unable to determine command line) 9.1 1 pyrunme s1 terminal ProbeSanityTest.fftc
The user has access to the python session as well as the python .exe, apparently this has been looked at by some people in spirent but weren't able to find the cause as to why some people just cant run the scripts, despite having full access to the python .exe
52 People are following this question.
