prosgarz35 commented on code in PR #3197:
URL: https://github.com/apache/james-project/pull/3197#discussion_r4083761084
##########
server/blob/blob-file/src/test/java/org/apache/james/blob/file/FileBlobStoreDAOTest.java:
##########
@@ -46,4 +46,28 @@ public BlobStoreDAO testee() {
public void mixingSaveReadAndDeleteShouldReturnConsistentState() {
}
+
+ @Override
+
@org.junit.jupiter.api.condition.DisabledOnOs(org.junit.jupiter.api.condition.OS.WINDOWS)
Review Comment:
> Isn't file locks an issue ? UNIX use it for correcness upon concurrency.
You are right regarding Windows file locking semantics: NTFS enforces
mandatory file locks on open file handles, which causes concurrency conflicts
during concurrent atomic replacements/deletions (concurrentSave... tests). On
Linux/POSIX systems, inode-based atomic rename(2) and advisory locks work
properly without concurrency issues
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
