Right, but we work around other issues that look like bugs. If our NativeFSLock fails because a file on windows is briefly unavailable, I think that's a bug. Whats wrong with pausing and waiting a short bit for a retry when Windows is detected and this issue is triggered.

On 4/27/10 12:50 PM, Uwe Schindler wrote:
No, the error is correct, the problem is a different one (outside of 
NativeFSLock):
On windows (vista or 7) some services like virus scanners (Microsoft Security 
Essentials, Avira Antivir and others) and the windows search service sometimes 
locks the whole dir/files in it for very short time. After disabling virus 
scanning and most importantly windows search for the lucene development 
folders, the problems are gone. This behavior is also the source of some 
chkdsks running after restart when using svn in parallel to windows search 
(this is a known bug in ntfs.sys of windows 7, event id 55 in syslogs).

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]

-----Original Message-----
From: Mark Miller [mailto:[email protected]]
Sent: Tuesday, April 27, 2010 6:31 PM
To: [email protected]
Subject: Re: LuceneJUnitResultFormatter sometimes fails to lock

Ah - didn't look closely. This is while making the lock, not trying to
acquire it for stdout locking. So that seems like a bug in our native
lock impl we should try and fix.

On 4/27/10 12:27 PM, Uwe Schindler wrote:
When aquiring a test lock it does not wait. It just is not able to
produce the file there. This happens sometimes on windows and has
nothing to do with the tests, is a problem of NativeLockF.

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]


-----Original Message-----
From: Mark Miller [mailto:[email protected]]
Sent: Tuesday, April 27, 2010 6:20 PM
To: [email protected]
Subject: Re: LuceneJUnitResultFormatter sometimes fails to lock

We might need a higher timeout. Its like 5 seconds now. Otherwise we
should try and isolate the problem.

- Mark

On 4/27/10 11:52 AM, Uwe Schindler wrote:
Windows?

-----

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

http://www.thetaphi.de<http://www.thetaphi.de/>

eMail: [email protected]

*From:* Shai Erera [mailto:[email protected]]
*Sent:* Tuesday, April 27, 2010 5:50 PM
*To:* [email protected]
*Subject:* LuceneJUnitResultFormatter sometimes fails to lock

Hi

I ran "ant test-core" today and hit this:

[junit] Exception in thread "main" java.lang.RuntimeException:
Failed
to
acquire random test lock; please verify filesystem for lock
directory
'C:\DOCUME~1\shaie\LOCALS~1\Temp\lucene_junit_lock' supports
locking
[junit] at


org.apache.lucene.store.NativeFSLockFactory.acquireTestLock(NativeFSLoc
kFactory.java:88)
[junit] at


org.apache.lucene.store.NativeFSLockFactory.makeLock(NativeFSLockFactor
y.java:127)
[junit] at


org.apache.lucene.util.LuceneJUnitResultFormatter.<init>(LuceneJUnitRes
ultFormatter.java:74)

All the tests still pass, but Ant reports a failure in the end.
Also,
this rarely happens, but I've run into it several times already.
Anyone
got an idea?

Shai



--
- Mark

http://www.lucidimagination.com

--------------------------------------------------------------------
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



--
- Mark

http://www.lucidimagination.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



--
- Mark

http://www.lucidimagination.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to