Comment 1 for bug 1436224

Hey Thomas - All the unit tests are ran before any code can be checked into the repository, and while we've had changes to this area of the code recently, I suspect we may have an environmental issues with the build? Maybe a mix of old and new code?

I'm guessing this is happening as part of a debian pkg build, on the same system, is it possible to reproduce the issue with `tox -e py27`, or to avoid the tox virtualenv, manually installing the .deb dependencies and running `python setup.py testr` outside of the debian pkg build?