Updates:
Status: Accepted
Labels: Target-2.5.1
Comment #1 on issue 593 by pekka.klarck: Ctrl-C does not support skipping
the teardown AND generating a report
http://code.google.com/p/robotframework/issues/detail?id=593
I can understand that the current behavior doesn't work very well if
teardowns take a lot of time. The proposed three step ctrl-c sequence
sounds somewhat complicated, though.
It would be easiest to simply change the current behavior so that teardowns
are skipped when ctr-c is pressed. Since the idea of pressing ctrl-c is to
exit immediately, that would actually make sense. The downside, and the
main reason why the functionality works as it currently does, is that not
running teardowns may leave the system under test into unstable state.
Should we send a question to rf-users (and NSN internal users list) and ask
what users think? If skipping teardowns is fine, we can do that already in
RF 2.5.1.
This functionality should probably work similarly also with fatal
exceptions, signals, and with `--RunMode ExitOnFailure`. With signals we
could potentially make SIGINT and SIGHUP behave differently.
Need to send a question about this
