selftest noise re _http_start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Low
|
Vincent Ladeuil |
Bug Description
This has been introduced just recently in bzr.dev. It doesn't happen in 0.91rc2. It happens on both python 2.4 and python 2.5. It doesn't actually break tests but it's ugly noise.
ian@possum:
testing: /home/ian/
/home/
/home/ian/
warn("You must install medusa (http://
Exception in thread Thread-2:
Traceback (most recent call last):
File "threading.py", line 442, in __bootstrap
self.run()
File "threading.py", line 422, in run
self.
File "/home/
httpd.
File "<string>", line 1, in settimeout
File "socket.py", line 136, in _dummy
raise error(EBADF, 'Bad file descriptor')
error: (9, 'Bad file descriptor')
[317/884 in 14s, 28 skipped] test_transport_
Traceback (most recent call last):
File "threading.py", line 442, in __bootstrap
self.run()
File "threading.py", line 422, in run
self.
File "/home/
httpd.
File "<string>", line 1, in settimeout
File "socket.py", line 136, in _dummy
raise error(EBADF, 'Bad file descriptor')
error: (9, 'Bad file descriptor')
[771/884 in 32s, 31 skipped] test_transport_
Traceback (most recent call last):
File "threading.py", line 442, in __bootstrap
self.run()
File "threading.py", line 422, in run
self.
File "/home/
httpd.
File "<string>", line 1, in settimeout
File "socket.py", line 136, in _dummy
raise error(EBADF, 'Bad file descriptor')
error: (9, 'Bad file descriptor')
[884/884 in 36s, 44 skipped] test_transport_
-------
Ran 884 tests in 36.894s
OK
44 tests skipped
tests passed
Changed in bzr: | |
status: | Confirmed → Fix Committed |
importance: | Undecided → Low |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
>>>>> "Ian" == Ian Clatworthy writes:
Ian> Public bug reported:
Ian> This has been introduced just recently in bzr.dev. It doesn't happen in
Ian> 0.91rc2. It happens on both python 2.4 and python 2.5. It doesn't
Ian> actually break tests but it's ugly noise.
I can't reproduce it, any hint about your setup ? OS ?
The strangest thing is that it happens during the test http
server start, and should break its initialization. So the test
should break too since noone is there to serve the requests.