All the failures are in tearDown, and they look like this:
Traceback (most recent call last):
Module unittest.case, line 360, in run
self.tearDown()
Module zodbbrowser.ftests.test_standalone, line 163, in tearDown
shutil.rmtree(self.tempdir)
Module shutil, line 252, in rmtree
onerror(os.remove, fullname, sys.exc_info())
Module shutil, line 250, in rmtree
os.remove(fullname)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\users\\mg\\appdata\\local\\temp\\2\\tmp1513gnzodbbrowser\\empty.fs'
It seems that when we start the server in a thread and then stop it, that server doesn't close the database. This is not a problem on Linux but a big problem on Windows.
Note that my Window Jenkins slave currently cannot run the tests easily, thanks to the Rackspace SSL download issues. For all the other projects I use pip 1.5 as a workaround, but this is impossible for zodbbrowser, thanks to two reasons:
no binary wheels for ZODB/zope.*/lxml
some zope.* packages use setup_requires which ends up downloading stuff from PyPI using setuptools, which is prone to the SSL checksum failures.
All the failures are in tearDown, and they look like this:
It seems that when we start the server in a thread and then stop it, that server doesn't close the database. This is not a problem on Linux but a big problem on Windows.
Note that my Window Jenkins slave currently cannot run the tests easily, thanks to the Rackspace SSL download issues. For all the other projects I use pip 1.5 as a workaround, but this is impossible for zodbbrowser, thanks to two reasons: