JDK-8278469 : Test java/nio/channels/FileChannel/LargeGatheringWrite.java times out
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 18,19,20
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: x86_64,aarch64
  • Submitted: 2021-12-09
  • Updated: 2024-03-05
  • Resolved: 2022-07-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 19 JDK 20
19 b31Fixed 20Fixed
Related Reports
Relates :  
JDK-8290252 - Add TEST.properties to java/nio/channels/FileChannel and move tests out of largeMemory sub-dir
Relates :  
JDK-8289526 - java/nio/channels/FileChannel/MapTest.java times out
Relates :  
JDK-8278369 - java/nio/channels/Channels/TransferTo.java hangs in testStreamContents
Relates :  
JDK-8289470 - java/nio/channels/Channels/ReadXBytes.java failed with "exit code: 137"
Description
----------System.out:(5/155)----------
Seed from RandomFactory = 7973809281479571012L
Writing 5368709122 bytes of data...
Wrote 2147483647 bytes
Wrote 2147483647 bytes
Timeout refired 960 times
----------System.err:(0/0)----------
----------rerun:(36/8290)*----------
Comments
The fix for this bug has not yet been sync'ed from JDK19.
08-07-2022
The fix for this bug is integrated in jdk-19+31-2177.
08-07-2022
Changeset: 11319c2a Author: Brian Burkhalter <bpb@openjdk.org> Date: 2022-07-07 22:36:08 +0000 URL: https://git.openjdk.org/jdk19/commit/11319c2aeb16ef2feb0ecab0e2811a52e845739d
07-07-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk19/pull/122 Date: 2022-07-07 22:25:10 +0000
07-07-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/9416 Date: 2022-07-07 20:36:43 +0000
07-07-2022
Linked JDK-8289526 to which this issue is almost certainly related as it is quite probably also to JDK-8278369 which is also linked.
07-07-2022
[~dcubed] Thanks for adding the hostname to the comment: very helpful! [~alanb] I broached the subject on #mach5support a couple of days ago and there was no response; I shall try again.
07-07-2022
Here's a log file snippet for the jdk-20+5-210-tier7 sighting: java/nio/channels/FileChannel/LargeGatheringWrite.java #section:main ----------messages:(6/253)---------- command: main -Xmx4G LargeGatheringWrite reason: User specified action: run main/othervm/timeout=240 -Xmx4G LargeGatheringWrite Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. elapsed time (seconds): 1121.444 ----------configuration:(0/0)---------- ----------System.out:(15/428)---------- Seed from RandomFactory = -1465090764079936852L Writing 5368709122 bytes of data... Wrote 5368709122 bytes Total of 5368709122 bytes written Checking length 1073741824 Checking length 1073741824 Timeout refired 960 times Checking length 536870912 Checking length 536870912 Checking length 536870912 Checking length 536870912 Checking length 536870912 Checking length 536870912 Checking length 1 Checking length 1 ----------System.err:(1/16)---------- STATUS:Passed. ----------rerun:(43/6516)*---------- The test PASSed while the timeout handler was running.
06-07-2022
We seem to have a lot of windows tests timing out at the moment - see also JDK-8289526 and JDK-8278369. I suspect this is all the same underlying problem.
04-07-2022
[~bpb] This test has started to timeout very frequently on Windows from about June 30, both openjdk/jdk19 and openjdk/jdk so may be an infrastructure issue rather than a JDK or test issue. I think it will need attention to understand why the execution times increased and maybe to see if the test case be dialled down to run in less time.
04-07-2022
Here's a log file snippet from the jdk-20+5-182-tier2 sighting: java/nio/channels/FileChannel/LargeGatheringWrite.java #section:main ----------messages:(6/253)---------- command: main -Xmx4G LargeGatheringWrite reason: User specified action: run main/othervm/timeout=240 -Xmx4G LargeGatheringWrite Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. elapsed time (seconds): 1083.406 ----------configuration:(0/0)---------- ----------System.out:(6/199)---------- Seed from RandomFactory = 5069676580147580464L Writing 5368709122 bytes of data... Timeout refired 960 times Wrote 5368709122 bytes Total of 5368709122 bytes written Checking length 1073741824 ----------System.err:(0/0)---------- ----------rerun:(40/5953)*---------- Please note that this sighting did not pass while the timeout handler was running.
30-06-2022
Here's a log file snippet from the jdk-20+5-181-tier2 sighting: java/nio/channels/FileChannel/LargeGatheringWrite.java #section:main ----------messages:(6/253)---------- command: main -Xmx4G LargeGatheringWrite reason: User specified action: run main/othervm/timeout=240 -Xmx4G LargeGatheringWrite Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. elapsed time (seconds): 1004.847 ----------configuration:(0/0)---------- ----------System.out:(15/427)---------- Seed from RandomFactory = 8443461428284579298L Writing 5368709122 bytes of data... Wrote 5368709122 bytes Total of 5368709122 bytes written Checking length 1073741824 Checking length 1073741824 Checking length 536870912 Checking length 536870912 Checking length 536870912 Timeout refired 960 times Checking length 536870912 Checking length 536870912 Checking length 536870912 Checking length 1 Checking length 1 ----------System.err:(1/16)---------- STATUS:Passed. ----------rerun:(40/5953)*---------- <snip> result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-20+5-181\windows-x64.jdk\jdk-20\bin\java' timed out (timeout set to 960000ms, elapsed time including timeout handling was 1004842ms). Please note that the test PASSed while the timeout handler was running.
30-06-2022