backtrace on canceled test

[email protected]
Newsgroups gmane.comp.python.twisted.bugs
Message-ID <[email protected]>
New submission from robertc <[email protected]>:

I hit control-C while running tests in trial.

While trial should stop on control-C, a backtrace isn't that useful. I'd suggest that:
 - the current test have a failure with the exception I caused logged
 - the test suite stop immediately
 - control return to the consol.e


  File "/usr/bin/trial", line 24, in <module>
    run()
  File "/usr/lib/python2.6/dist-packages/twisted/scripts/trial.py", line 361, in run
    test_result = trialRunner.run(suite)
  File "/usr/lib/python2.6/dist-packages/twisted/trial/runner.py", line 813, in run
    return self._runWithoutDecoration(test)
  File "/usr/lib/python2.6/dist-packages/twisted/trial/runner.py", line 839, in _runWithoutDecoration
    run()
  File "/usr/lib/python2.6/dist-packages/twisted/trial/runner.py", line 834, in <lambda>
    run = lambda: suite.run(result)
  File "/usr/lib/python2.6/dist-packages/twisted/trial/runner.py", line 291, in run
    TestSuite.run(self, result)
  File "/usr/lib/python2.6/dist-packages/twisted/trial/unittest.py", line 1496, in run


----------
Type     : defect
Component: trial
Keywords : 
Priority : normal
Nosy     : 
----------
http://twistedmatrix.com/trac/ticket/3975
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.