post-test failures in bzr.dev

[Martin Pool]

On 05/04/2006, at 11:25 PM, Jamie Wilkinson wrote:

> Just pulled down from bzr.dev, and now I get these errors after the
> testsuite has finished:
>
> OK
> Deleting test root /home/jaq/src/bzr/bzr.jaq/test0000.tmp...
>
> tests passed
> Error in atexit._run_exitfuncs:
> Traceback (most recent call last):
>   File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs
>     func(*targs, **kargs)
>   File "/usr/lib/python2.4/logging/__init__.py", line 1332, in  
> shutdown
>     h.flush()
>   File "/usr/lib/python2.4/logging/__init__.py", line 718, in flush
>     self.stream.flush()
> ValueError: I/O operation on closed file
> Error in sys.exitfunc:
> Traceback (most recent call last):
>   File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs
>     func(*targs, **kargs)
>   File "/usr/lib/python2.4/logging/__init__.py", line 1332, in  
> shutdown
>     h.flush()
>   File "/usr/lib/python2.4/logging/__init__.py", line 718, in flush
>     self.stream.flush()
> ValueError: I/O operation on closed file
>
> There isn't anything useful in ~/.bzr.log

Yes, I'm seeing this too.  Someone thought it was because of a change  
in Python in Ubuntu Dapper rather than something in our source.  (It  
should be easy to answer by testing an old version.)

-- 
Martin Pool