[
https://issues.apache.org/jira/browse/LUCENE-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973292#comment-13973292
]
Uwe Schindler commented on LUCENE-5612:
---------------------------------------
bq. I'm not sure what you mean, Uwe - I just ran the smoke tester against the
4.7.2 RC2 on Win7+Cygwin, and it passed:
Cygwin is not windows. It does definitely does not work with a real Win32
binary. On cygwin with cygwin python it works, because all filenames are
forward slashes without drive latter and so on.
If you fix this to work in windows (Cygwin is No-go for me, because java
itsself is not cygwin compatible), i would run smoketester on window jenkins
(which has no cygwin!!!!!), but only ever with a real windows python compiled
against win32 kernel API (not a fake-glibc wrapper).
But this is a test that should run in our test suite. And the ANT task is so
simple, very easy to setup parallel runs. It is just a timeout missing, so the
test can end after a while.
Sorry, -1 to add this to smoketester only
> LockStressTest fails always with NativeFSLockFactory
> ----------------------------------------------------
>
> Key: LUCENE-5612
> URL: https://issues.apache.org/jira/browse/LUCENE-5612
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Blocker
> Fix For: 4.8
>
> Attachments: LUCENE-5612-tester.patch
>
>
> I was looking at this, because i wanted to remove the static map inside
> NativeFSLockFactory (no particular reason: it just smells bad, we require
> java7, and you get overlappingexception as of java6 so its unnecessary).
> Before changing any code, i wanted to run lockstresstest first, just to
> ensure it works: but it fails always. Simple works fine always.
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.RuntimeException: lock was double acquired at
> org.apache.lucene.store.VerifyingLockFactory$CheckedLock.verify(VerifyingLockFactory.java:67)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
