test_client fails on cygwin #143

New Issue

zooko · 2007-09-22T16:44:45Z

zooko commented

2007-09-22 16:44:45 +00:00

This happens on our cygwin buildslave as well as on my cygwin on Parallels v2 on my Macbook Pro:

===============================================================================
[FAIL]: allmydata.test.test_runner.RunNode.test_client

Traceback (most recent call last):
  File "/cygdrive/c/playground/allmydata/tahoe/src/allmydata/test/test_runner.py", line 167, in _started
    self.failUnlessEqual(rc, 0, errstr)
twisted.trial.unittest.FailTest: rc=1, OUT: '', ERR: 'never saw process go away
not restarting
'

This happens on our cygwin buildslave as well as on my cygwin on Parallels v2 on my Macbook Pro: ``` =============================================================================== [FAIL]: allmydata.test.test_runner.RunNode.test_client Traceback (most recent call last): File "/cygdrive/c/playground/allmydata/tahoe/src/allmydata/test/test_runner.py", line 167, in _started self.failUnlessEqual(rc, 0, errstr) twisted.trial.unittest.FailTest: rc=1, OUT: '', ERR: 'never saw process go away not restarting ' ```

zooko added the

labels 2007-09-22 16:44:45 +00:00

zooko added this to the 0.6.0 milestone 2007-09-22 16:44:45 +00:00

zooko self-assigned this 2007-09-22 16:44:45 +00:00

zooko commented

2007-09-22 22:46:06 +00:00

Okay, SIGINT doesn't cause the Python interpreter to quit under cygwin, but it does print "Keyboard Interrupt" to stdout when it receives that signal. (Could have something to do with #136 ?)

How about if do_stop() uses SIGTERM?

Okay, SIGINT doesn't cause the Python interpreter to quit under cygwin, but it does print "Keyboard Interrupt" to stdout when it receives that signal. (Could have something to do with #136 ?) How about if do_stop() uses SIGTERM?

zooko removed their assignment 2007-09-22 22:46:06 +00:00

warner was assigned by zooko

2007-09-22 22:46:06 +00:00

zooko commented

2007-09-22 22:49:47 +00:00

No, this can't have anything to do with #136 (i.e. with Twisted ticket #733) because I did this with a plain cygwin python interpreter that hadn't imported Twisted or anything else.

No, this can't have anything to do with #136 (i.e. with [Twisted ticket #733](http://twistedmatrix.com/trac/ticket/733)) because I did this with a plain cygwin python interpreter that hadn't imported Twisted or anything else.

zooko commented

2007-09-22 23:05:30 +00:00

(http://twistedmatrix.com/pipermail/twisted-python/2006-May/013115.html)

excerpt from that page:

Just to add more informations:
when killing a normal Python process with TERM, the Interpreter
terminates without calling the functions registered with atexit.

Now this is strange because the MSDN says that, by default, SIGTERM is
ignored and the Python documentation says that only an handler for
SIGINT is installed.

(http://twistedmatrix.com/pipermail/twisted-python/2006-May/013115.html) excerpt from that page: ``` Just to add more informations: when killing a normal Python process with TERM, the Interpreter terminates without calling the functions registered with atexit. Now this is strange because the MSDN says that, by default, SIGTERM is ignored and the Python documentation says that only an handler for SIGINT is installed. ```

zooko commented

2007-09-23 15:36:34 +00:00

fixed by changeset:93efd2902ee4626b

zooko added the

fixed

label 2007-09-23 15:36:34 +00:00

zooko closed this issue

2007-09-23 15:36:34 +00:00

warner added

code

and removed

unknown