Error running tests for plugins . . .
mnordhoff at mattnordhoff.com
Fri Jul 3 22:55:50 BST 2009
Russel Winder wrote:
> Sorry this is turning into a bit of a mission :-(
> On the other hand, it has been solved :-)
> On Fri, 2009-07-03 at 18:57 +0000, Matt Nordhoff wrote:
> [ . . . ]
>> 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.
> OK, on the grounds that python-codespeak-lib is supposed to contain
> py.test I installed that. It didn't do any good. Material gets
> installed into /usr/share/pyshared but whatever is needed is not found,
> I got the same result.
<http://codespeak.net/py/dist/download.html> says "As of July 2009
pytest/pylib 1.0 RPMs and Debian packages are not yet available."
>> ~/.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. :-\
> It is getting surprisingly irritating :-(
> However, on reading the output in .bzr.log, I spotted that finally I was
> seeing an error in the code I was writing. Yay, bug found, bug fixed,
> tests now work :-)
> Thanks for your help, sorry for the hassle. I can now do some Friday
> evening imbibement of beverage.
More information about the bazaar