-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b17
-
sparc
-
solaris
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8270013 | 11.0.13-oracle | Thejasvi Voniadka | P3 | Resolved | Fixed | b02 |
JDK-8273076 | 11.0.13 | Christoph Langer | P3 | Resolved | Fixed | b05 |
There has been a recent change to Oracle's internal test environment that now causes a couple of HTTP Client tests to timeout before they have had a chance to complete their execution, resulting in what ( incorrectly ) appears as a test failure / error. The solution is for these tests to specify an explicit relatively long timeout, so that they are allow enough time to run on extremely slow systems.
The tests in question are:
test/jdk/java/net/httpclient/DigestEchoClientSSL.java
test/jdk/java/net/httpclient/ProxyAuthDisabledSchemesSSL.java
The tests in question are:
test/jdk/java/net/httpclient/DigestEchoClientSSL.java
test/jdk/java/net/httpclient/ProxyAuthDisabledSchemesSSL.java
- backported by
-
JDK-8270013 Add explicit timeout to several HTTP Client tests
-
- Resolved
-
-
JDK-8273076 Add explicit timeout to several HTTP Client tests
-
- Resolved
-