Comment #2 on issue 1651 by pekka.klarck: Timeout in 2.7, 2.8 does not
interrupt SSHLibrary's Execute Command keyword
http://code.google.com/p/robotframework/issues/detail?id=1651
As Mikko already wrote, we just fixed an issue in SSHLibrary that caused
Execute Command to ignore timeouts, signals, etc. The reported problem
should thus be fixed now.
RF 2.6.3 and earlier are probably able to stop Execute Command because they
use different timeout implementation internally. That old implementation
was a hack that caused serious performance problems and it was replaced by
a much better operating system dependent implementation in RF 2.7 (issue
871). The problems caused by the old implementation were so bad that we
don't consider taking it back. If similar issues are found with other
keyword, they need to be handled case-by-case.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
