[openstack-dev] [testing] moving testrepository *outside* the tox venv

Ian Cordasco ian.cordasco at RACKSPACE.COM
Sat Jul 11 03:54:52 UTC 2015

On 7/10/15, 18:34, "Monty Taylor" <mordred at inaugust.com> wrote:

>On 07/10/2015 07:19 PM, Robert Collins wrote:
>> On 10 July 2015 at 01:59, Morgan Fainberg <morgan.fainberg at gmail.com>
>>> Or a database per python major version (or at least gracefully handle
>>>the incompatibility).
>> So that would partition the data, and the whole point of test
>> *repository* is that it builds a database across all your tests to
>> answer useful questions.
>Totally understand that.
>On the other hand ...
>a) is that setup/behavior common enough to be more important than:
>b) the dbm file format mess is both annoying and confusing
>I get the theory of why - but it's also a common thing that provides rage.

Just as an example, I went to fix a pypy error and was receiving an
exception about not being able to import _bsddb. The fix? Remove
.testrepository. I understand testrepository is meant to be a metatool,
but it provides very bizarre problems in some cases. I understand why we
use it, but the situation really need to improve the situation.

More information about the OpenStack-dev mailing list