On some of our machines the test java/nio/channels/FileChannel/LoopingTruncate.java sometimes fails with
java.io.IOException: There is not enough space on the disk
       at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method)
       at java.base/sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:74)
       at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:137)
       at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:102)
       at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:72)
       at java.base/sun.nio.ch.FileChannelImpl.implWrite(FileChannelImpl.java:371)
       at java.base/sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:351)
       at LoopingTruncate.main(LoopingTruncate.java:56)
       at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
       at java.base/java.lang.reflect.Method.invoke(Method.java:565)
       at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
       at java.base/java.lang.Thread.run(Thread.java:1447)

Looks like the machines have only few disc space available and the test creates a very large file.
Should we maybe catch the IOException and then throw a SkippedException in case the "large file creation" fails ?
(the real test later seems to be the truncate operation )