-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b75
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8136193 | emb-9 | Joe Darcy | P2 | Resolved | Fixed | team |
The test
java/util/concurrent/ConcurrentHashMap/ConcurrentAssociateTest.java
has failed 90% of a couple hundred runs due to timeouts when run on a solaris-sparc which is a zone on a host with 256 cpu. Increasing the timeout value to 12 or so allows this to pass sometimes but it takes up to 14 or 15 minutes. While this may be due to the zone sharing resources, availableProcessors() still returns 256, and this test can take an unreasonable amount of time for 1 test.
If this is not a bug, can the test put a cap on this value at 24 or 32 so that it runs in a reasonable amount of time?
java/util/concurrent/ConcurrentHashMap/ConcurrentAssociateTest.java
has failed 90% of a couple hundred runs due to timeouts when run on a solaris-sparc which is a zone on a host with 256 cpu. Increasing the timeout value to 12 or so allows this to pass sometimes but it takes up to 14 or 15 minutes. While this may be due to the zone sharing resources, availableProcessors() still returns 256, and this test can take an unreasonable amount of time for 1 test.
If this is not a bug, can the test put a cap on this value at 24 or 32 so that it runs in a reasonable amount of time?
- backported by
-
JDK-8136193 ConcurrentHashMap/ConcurrentAssociateTest.java, times out 90% of time on sparc with 256 cpu.
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-