JDK-8174810 : java/io/FileInputStream/LargeFileAvailable.java timed out intermittently
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: os_x
  • CPU: x86_64
  • Submitted: 2017-02-13
  • Updated: 2017-04-28
  • Resolved: 2017-04-28
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.
Other
tbd_minorResolved
Related Reports
Relates :  
JDK-8176337 - Mark several tests as intermittently failing
Relates :  
JDK-8176846 - (fc) Increase timeouts of and instrument some tests using FileChannel#write
Relates :  
JDK-8175042 - Add success message to java/io/FileInputStream/LargeFileAvailable.java
Relates :  
JDK-8140263 - (ch) java/nio/channels/FileChannel/Transfer.java timed out
Relates :  
JDK-8173386 - java/nio/channels/FileChannel/LoopingTruncate.java timeout
Relates :  
JDK-8179452 - Remove "intermittent" key from some tests which appear no longer to fail
Description
java/io/FileInputStream/LargeFileAvailable.java


Test completed but Agent timed out at the end.

----------System.out:(3/229)----------
Skipped 3110608882 bytes, available() returns 2147483647, remaining 4294967300
Skipped 10 bytes, available() returns 2147483647, remaining 4294967290
Skipped 3110608882 bytes, available() returns 1184358408, remaining 1184358408
----------System.err:(3/36)----------

JavaTest Message:  Test complete.

result: Error. Agent error: java.lang.Exception: Agent 11 timed out with a timeout of 600 seconds; check console log for any additional details
Comments
Build #2033: Failures only and always fail at Mach 5 macosx-amd64 scaab269.us or scaab270.us (always pass at other Mac machines, even the same OS version)
26-02-2017
The output suggests the test completed. I wonder if the timeout is related to cleanup. Has anything in the infrastructure changed recently that would lead to the removal of large files taking a long time? Can we get a list of machines where this is happen, just in case it's one specific machine. Also which JDK is jtreg being run on?
16-02-2017