selftest on win32

[Martin Pool]

On Mon, Nov 10, 2008 at 8:04 PM, Alexander Belchenko <bialix at ukr.net> wrote:
> Martin Pool пишет:
>>
>> On Mon, Nov 10, 2008 at 1:01 PM, Mark Hammond <mhammond at skippinet.com.au>
>> wrote:
>>>>
>>>> If you want to talk about
>>>> particular messages, post them here (or refer to older threads.)
>>>
>>> A fair bit of noise (55 failures at last count) are along the lines of:
>>>
>>> """
>>> FAIL: test_push_only_pushes_history
>>> (bzrlib.tests.blackbox.test_push.TestPush)
>>> vvvv[log from
>>> bzrlib.tests.blackbox.test_push.TestPush.test_push_only_pushes_history]
>>> ...
>>> LockContention: Could not acquire lock
>>>
>>> "O:/window~1/testbzr-ds0uvn.tmp/.test_push_only_pushes_history/work/push-b/.
>>> bzr/checkout/dirstate"
>>> """
>>
>> I think it would be a small step forward to turn these into expected
>> failures, pointing at the bug number describing the problem.  (There
>> may already be one.)
>
> https://bugs.launchpad.net/bzr/+bug/206406

(thanks)

I just added:

> In general I think this happens when we have aliasing of two objects pointing to a single on disk file, and *that* typically happens when we're passing around a filename rather than an object reference.  For instance the tests commonly set up a branch using the object api, but then actually run the tests through a run_bzr command line, which will try to reopen them separately.

-- 
Martin <http://launchpad.net/~mbp/>