Error running tests for plugins . . .

[Matt Nordhoff]

Russel Winder wrote:
> Matt,
> 
> Thanks for thinking clearly and spotting the important facts.  I should
> have done that first myself :-)
> 
> On Fri, 2009-07-03 at 18:16 +0000, Matt Nordhoff wrote:
>> Russel Winder wrote:
>>> I wanted to run the tests for the installed bzrtools plugin.  I had
>>> thought "bzr selftest bzrtools" might do teh trick.  However, this
>>> results in the following.  Am I just doing something stupid, or is this
>>> a Bazaar bug?
>>>
>>> Thanks.
>>>
>>>
>>>  |> bzr selftest bzrtools
>>> bzr: ERROR: exceptions.AttributeError: 'module' object has no attribute 'TransportTestProviderAdapter'
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/upload/tests/test_upload.py", line 44, in <module>
>>>     test_transport_implementations.TransportTestProviderAdapter):
>>> AttributeError: 'module' object has no attribute 'TransportTestProviderAdapter'
>> Looks like the bzr-upload plugin's test suite isn't compatible with your
>> version of bzr. If it hasn't been fixed in a newer version, file a bug
>> against bzr-upload.
> 
> I removed bzr-upload and that seems to have done the trick for that
> problem.  I will try with a branch of the plugin mainline before
> reporting a bug though -- this may just be a bleading edge consistency
> problem.
> 
>> I guess you'll have to temporarily uninstall bzr-upload so you can run
>> the test suite for other plugins.
> 
> Hummm:
> 
> |> bzr selftest bzrtools
> bzr: ERROR: No module named py
> You may need to install this Python library separately.
> |>
> 
> OK so there is progress but not success :-(
> 
> As far as I can tell Ubuntu has no package python-py, so I guess I have
> to start guessing which package has the need stuff in.  The problem is I
> don't know what stuff is needed :-((

Eh. There's a library called py that includes several different things,
including some related to testing. I guess one of your plugins uses it.

<http://codespeak.net/py/dist/>

~/.bzr.log should contain a traceback showing which plugin wanted it.
Then you can do what you want, installing py or disabling that plugin.
Your choice. Shrug.

I didn't expect testing plugins to be this complicated. That's a pain. :-\
--