deactivate tests that cause a symlink pointing to nothing In the concerned tests, a file named sameOtherFile is created, and at some point in the afterClass method in AbstractFileSystemTestCase.java, this symlink points to nothing, which is due to a bug in commons-io 2.8.0. Those tests are deactivated, but should be activated again once the bug in commons-io has been fixed. See bug IO-692 in the bug dashboard on issues.apache.org website.
upstream applies various methods to look for the native library and falls back to pure java if linking fails. Here we just load the library from /usr/lib/jni and quit immediately if linking fails.
Skip non-functional test From: Adam Borowski <kilobyte@angband.pl> Date: Mon, 15 Jan 2018 00:11:55 +0100 . This is caused by an assumption that link count of a directory without any hardlinks is 2 (or more general, 2 plus number of subdirectories). This is true on 70's sysvfs and descendants like ext*, and emulated by most filesystems, but not all. . Btrfs and some remote filesystems instead always give 1 (directory hardlinks being an unthing on any filesystems I'm aware of, symlinks and reflinks have a different semantic and thus neither is shown in link count). . Thus, this test is bogus and should be skipped.
Disable the affected test by following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973070#22 . FIXME: Needs checking whether the test might be OK for future commons-io versions
