On Sep 30, 2011, at 6:28 PM, Alan Bateman wrote: > Kelly O'Hair wrote: >> Has anyone seen this testcase fail like this? >> >> FAILED: java/nio/channels/FileChannel/Transfers.java >> >> ACTION: main -- Failed. Execution failed: `main' threw exception: >> java.lang.RuntimeException: Some tests failed >> REASON: Assumed action based on file name: run main Transfers >> TIME: 3.337 seconds >> messages: >> command: main Transfers >> reason: Assumed action based on file name: run main Transfers >> elapsed time (seconds): 3.337 >> STDOUT: >> From file channel: 0 1 2 3 4 5 6 7 8 9 15 16 17 31 32 33 63 64 65 127 128 >> 129 255 256 257 511 512 513 1023 1024 1025 2047 2048 2049 4095 4096 4097 >> 8191 8192 8193 16383 16384 16385 32767 >> From user channel: 0 1 2 3 4 5 6 7 8 9 15 16 17 31 32 33 63 64 65 127 128 >> 129 255 256 257 511 512 513 1023 1024 1025 2047 2048 2049 4095 4096 4097 >> 8191 8192 8193 16383 16384 16385 32767 >> To file channel: 0 >> FAILURE: FileChannel, offset 0, length 1 >> Transfers$Failure: Wrong position: 0 (expected 1) >> at Transfers$FileTarget.verify(Transfers.java:316) >> at Transfers.testTo(Transfers.java:449) >> at Transfers.main(Transfers.java:527) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:474) >> at >> com.sun.javatest.regtest.MainAction$SameVMRunnable.run(MainAction.java:680) >> at java.lang.Thread.run(Thread.java:722) >> .... >> goes on forever ... :^( >> >> -kto > 10.04 = 2.6.32 which I think is the kernel version where sendfile was updated > to use splice and support sending to file descriptors connected to a file. If > I recall correctly it didn't update the file position causing the above > failure. Updating the kernel will likely fix this issue and I've verified > that it doesn't happen with 10.10 (2.6.35) and 11.04 (2.6.38). > > -Alan.
FYI.. On my Ubuntu 10.04 system it had 2.6.32-33, and after a 'aptitude full-upgrade' and reboot I had 2.6.32-34 and the problem seems to have gone away. -kto
