Hi Eric, do the filelock related fails only occur in the filelock module, or do they occur in other modules too? If the former, we should focus on the deletion issues. File locking on Windows is always good for headaches :-/ and we should keep them for later.
About file deletion fails: Do you have examples? I think we should use our FileUtils.deleteQuietly() for deletion in all unit tests. And maybe improve the util method as necessary (add a delete on vm shutdown) If file deletion in production methods does not work, I need concrete examples. My windows system here is very limited. I can only use it for simple test cases, no chance to build the whole archiva stack on it. Thank you and regards Martin Am 20. Februar 2020 14:47:45 MEZ schrieb Eric Barboni <[email protected]>: >Hi Martin, > Others test issues are more difficult to handle (about 350). > > Deletion is almost impossible due to access denied, still locked file. > >The stress test is failing a lot of time >org.apache.archiva.common.filelock.DefaultFileLockManagerTest.testWrite >org.apache.archiva.common.filelock.DefaultFileLockManager.writeFileLock(DefaultFileLockManager.java:222) > cannot access to file, used by another processus > >Regards >Eric > >-----Message d'origine----- >De : Martin Stockhammer <[email protected]> >Envoyé : vendredi 14 février 2020 08:37 >À : [email protected] >Objet : Re: Test fails( on Windows) > >Hi Eric, > >sorry, I missed your last mail about the filelock issue. I will check >the PR today. > >Regards > >Martin > >On 14.02.20 01:09, Eric Barboni wrote: >> Hi, >> Jumping late in the conversation for the failing test on windows. >> >> -- This message was sent from mobile phone.
