Traceback (most recent call last):The new unit tests needed a test fixture and it looks like the setup method is causing this.
File "/usr/lib/pymodules/python2.5/nose/case.py", line 364, in setUp
try_run(self.inst, ('setup', 'setUp'))
File "/usr/lib/pymodules/python2.5/nose/util.py", line 487, in try_run
return func()
File "/home/tlow/projects/tomstvutil/0.0.1dev/tests/test_tomstv.py", line 22, in setUp
ignore_hidden=False)
File "build/bdist.linux-i686/egg/scripttest/__init__.py", line 73, in __init__
File "build/bdist.linux-i686/egg/scripttest/__init__.py", line 203, in clear
File "/usr/lib/python2.5/shutil.py", line 175, in rmtree
rmtree(fullname, ignore_errors, onerror)
File "/usr/lib/python2.5/shutil.py", line 180, in rmtree
onerror(os.remove, fullname, sys.exc_info())
File "/usr/lib/python2.5/shutil.py", line 178, in rmtree
os.remove(fullname)
OSError: [Errno 16] Device or resource busy: '/home/tlow/projects/tomstvutil/0.0.1dev/tests/test-output/.tv/.nfs00000000000005ea00000004'
Hopefully some Googling with turn up something and the problem won't hold up the coding too long which was going rather well the last few days.
OK, the .nfs* file is due to silly renaming. Something crashed and an unlinked file got left behind. Now I just have to figure out what that "something" was. And I learned a new piece of trivia. ;-)
ReplyDelete