Currently working on one of the feature but while running full build (mvn
-Pcontrib-check clean install) at NIFI root, as suggested in Contribution
Guide, the build is failing in other module in Test scope.
I am certain it's not in my module as it's coming in master branch as well. And
I am hitting it consistently always.
Pasted the error stack in the end of mail.
I tried searching about it and figured out there is a similar issue reported
and it's still unresolved.
Also have read somewhere that it is OK to skip it.
But that post is little older (around May), so is this still an issue?
So should I just skip this?
What is the flag to skip only single test and not all?
Running org.wali.TestMinimalLockingWriteAheadLog
Tests run: 12, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 7.901 sec <<<
FAILURE! - in org.wali.TestMinimalLockingWriteAheadLog
testRecoverFileThatHasTrailingNULBytesAndTruncation(org.wali.TestMinimalLockingWriteAheadLog)
Time elapsed: 0.015 sec <<< ERROR!
java.nio.channels.OverlappingFileLockException: null
at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255)
at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152)
at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1063)
at java.nio.channels.FileChannel.lock(FileChannel.java:1053)
at
org.wali.MinimalLockingWriteAheadLog.<init>(MinimalLockingWriteAheadLog.java:187)
at
org.wali.MinimalLockingWriteAheadLog.<init>(MinimalLockingWriteAheadLog.java:108)
at
org.wali.TestMinimalLockingWriteAheadLog.testRecoverFileThatHasTrailingNULBytesAndTruncation(TestMinimalLockingWriteAheadLog.java:472)
Results :
Tests in error:
TestMinimalLockingWriteAheadLog.testRecoverFileThatHasTrailingNULBytesAndTruncation:472
╗ OverlappingFileLock
