Comment #2 on issue 648 by spielmann.robert: Signaling tests fail if
interpreter is full path on windows
http://code.google.com/p/robotframework/issues/detail?id=648
What I can say about this is that the tests don't fail, they simply don't
run. Test execution hangs at the first test. I did:
python run_atests.py C:\[path]\Python27.exe --exclude "non windows"
robot\running\stopping_with_signal.txt
If I hit Ctrl+C, I get "Second signal will force exit.", then the test
fails, and all following tests fail as well. It seems to me that the Python
process did get the signal, but didn't react to it in the way expected by
the test. Can this have something to do with the way the runner script
invokes Python?
See the attached report for details.
Attachments:
report.html 29.2 KB
