Hi Tony and Andreas,

Le 05/12/2020 à 02:22, tony mancill a écrit :
On Wed, Dec 02, 2020 at 08:59:16PM +0100, Andreas Tille wrote:
Control: tags -1 help

I wonder whether some Java expert might be able to clarify the
situation in bug #929530.

Hi Andreas,

[...]

The bad news is that tests are consistently failing.  Specifically, the
code [1] that runs after this test [2] fails consistently while trying
to clean up after the test with the error below:

[1] 
https://salsa.debian.org/med-team/libsis-base-java/-/blob/master/source/java/ch/systemsx/cisd/base/tests/AbstractFileSystemTestCase.java#L139
[2] 
https://salsa.debian.org/med-team/libsis-base-java/-/blob/master/sourceTest/java/ch/systemsx/cisd/base/unix/UnixTests.java#L121


Running testTouchSymLinkAndFileRealtimeTimer
Could not delete the directory 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 
exceptions: [java.io.IOException: Unable to delete file: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink]
Could not delete the directory 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests in second try 
because: 1 exceptions: [java.io.IOException: Unable to delete file: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink]
Exception in thread "main" org.apache.commons.io.IOExceptionList: 1 exceptions: 
[java.io.IOException: Unable to delete file: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink]
        at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:345)
        at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1206)
        at 
ch.systemsx.cisd.base.tests.AbstractFileSystemTestCase.afterClass(AbstractFileSystemTestCase.java:139)
        at ch.systemsx.cisd.base.unix.UnixTests.main(UnixTests.java:495)
        at ch.systemsx.cisd.base.AllTests.main(AllTests.java:56)
Caused by: java.io.IOException: Unable to delete file: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink
        at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1425)
        at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:338)
        ... 4 more
Caused by: java.nio.file.NoSuchFileException: 
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someLink
        at 
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
        at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
        at 
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
        at 
java.base/sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
        at 
java.base/sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:149)
        at 
java.base/sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99)
        at java.base/java.nio.file.Files.readAttributes(Files.java:1763)
        at java.base/java.nio.file.Files.size(Files.java:2380)
        at org.apache.commons.io.file.PathUtils.deleteFile(PathUtils.java:361)
        at org.apache.commons.io.file.PathUtils.delete(PathUtils.java:304)
        at org.apache.commons.io.file.PathUtils.delete(PathUtils.java:280)
        at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1423)
        ... 5 more

However the symlink *is* present after the build (I have to remove it from
the build tree manually), so I don't know yet whether this is an issue
with the code on this architecture or something about how I'm using the
schroot on the porterbox.
>

I've investigated and found the issue was in commons-io, as was pointed out by Bernd Rinn [1], because it does not remove symlinks to unexisting files properly, since version 2.8.0.

Still, I'm also having the issue on amd64.

I've checked the patch B. Rinn proposed in [1] for commons-io fixes the issue in amd64 and arm64.

Now I will prepare an upload of libsis-base-java avoiding to raise this issue and fill an appropriate bug report for commons-io.


In any event, my inclination is to close the unaligned access bug and
open a new bug for the test failure on this architecture.  I can't
reproduce it on amd64.
>
In that case I agree we could close the unaligned access bug.

Cheers,
tony


All the best,
Pierre

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973070#54

Reply via email to