I think that is because a bzr hook that expects to be run only during a bzr TestCase has fired during something that's not actually a bzr test case. I'm not sure why that would be. Perhaps some code is kind of half using bzrlib test facilities without properly initializing them, or perhaps an earlier test ended abruptly without cleaning up. On 19 November 2011 02:36, Gary Poster