> I'd expect anyone running on Windows to see these test failures.
>
> Andi..
>
So what do you think about this issue - can we ignore this or claim it's a
windows bug or hope that 'just' the test code is wrong?
I'd suggest to at least apply the mentioned fix (i.e. uncomment the close
call in t
> Well, sure, not running the code that breaks solves the problem. But can
you
> then run the tests multiple times ?
>
[Thomas Koch] note that previously closeStore() was not called, but now when
calling it the test_PyLucene runs OK.
And yes I can run tests several times- on PyLucene2.9 the index
On Apr 14, 2011, at 1:13, "Thomas Koch" wrote:
> Hi,
> I've observed some tests failing on my windows build of PyLucene.
> Tested with PyLucene 2.9(.2) and PyLucene 3.1(.0) (latest) with Python 2.6.
>
> The problem is with test_PyLucene.py and test_PythonDirectory.py and looks
> like some file
I have to add some detail: after applying the mentioned fix to
test_PythonDirectory.py both tests run OK with PyLucene2.9! But with
PyLucene3.1 it's a different story: test_PythonDirectory.py is OK but
test_PythonDirectory.py still fails (see output I sent in previous mail).
Regards,
Thomas
> --
