-
Bug
-
Resolution: Fixed
-
P4
-
22
-
b25
-
x86_64
-
os_x
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8321671 | 21.0.3-oracle | Ramesh Gangadhar | P4 | Resolved | Fixed | b01 |
| JDK-8322392 | 21.0.3 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
| JDK-8321672 | 17.0.11-oracle | Ramesh Gangadhar | P4 | Resolved | Fixed | b01 |
| JDK-8324924 | 17.0.11 | Amos SHI | P4 | Resolved | Fixed | b01 |
| JDK-8321673 | 11.0.23-oracle | Ramesh Gangadhar | P4 | Resolved | Fixed | b01 |
| JDK-8324962 | 11.0.23 | Amos SHI | P4 | Resolved | Fixed | b01 |
java/nio/channels/DatagramChannel/Connect.java
Here's a snippet from the log file:
#section:main
----------messages:(10/295)----------
command: main Connect
reason: Assumed action based on file name: run main Connect
started: Fri Jun 23 03:57:01 GMT 2023
Mode: agentvm
Agent id: 15
Timeout refired 480 times
Timeout information:
--- Timeout information end.
finished: Fri Jun 23 04:06:55 GMT 2023
elapsed time (seconds): 593.589
----------configuration:(12/1522)----------
<snip>
result: Error. Agent error: java.lang.Exception: Agent 15 timed out with a timeout of 480 seconds; check console log for any additional details
The log file has no indicators of why the test timed out. I did
a quick check for this history of this test and most runs take
less than one second.
- backported by
-
JDK-8321671 java/nio/channels/DatagramChannel/Connect.java timed out
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Open
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk11u-dev/46e4ad2b
-
Commit
openjdk/jdk17u-dev/0eb33447
-
Commit
openjdk/jdk21u-dev/5d328605
-
Commit
openjdk/jdk/570dffb1
-
Review
openjdk/jdk11u-dev/2478
-
Review
openjdk/jdk17u-dev/2162
-
Review
openjdk/jdk21u-dev/15
-
Review
openjdk/jdk21u-dev/16
-
Review
openjdk/jdk/16661