-
Bug
-
Resolution: Fixed
-
P4
-
7
-
b03
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8313731 | 8u401 | Abhishek N | P4 | Resolved | Fixed | b01 |
Currently, all RMI tests are run in othervm mode because of the following lines in jdk/test/TEST.ROOT (edited for brevity):
# Tests that must run in othervm mode
othervm.dirs=... java/rmi ... sun/rmi ...
In addition, the following lines in TEST.ROOT enforce exclusive access (edited for brevity):
# Tests that cannot run concurrently
exclusiveAccess.dirs=java/rmi/Naming
The /othervm declaration should be added to all the RMI tests and the RMI directories removed from the othervm.dirs property. Most, but not all of the RMI tests currently declare /othervm explicitly already. Later, if there are any RMI tests that can run in agentvm mode, the othervm declaration can be removed from them.
# Tests that must run in othervm mode
othervm.dirs=... java/rmi ... sun/rmi ...
In addition, the following lines in TEST.ROOT enforce exclusive access (edited for brevity):
# Tests that cannot run concurrently
exclusiveAccess.dirs=java/rmi/Naming
The /othervm declaration should be added to all the RMI tests and the RMI directories removed from the othervm.dirs property. Most, but not all of the RMI tests currently declare /othervm explicitly already. Later, if there are any RMI tests that can run in agentvm mode, the othervm declaration can be removed from them.
- backported by
-
JDK-8313731 TEST_BUG: update RMI tests to declare othervm explicitly
- Resolved
- relates to
-
JDK-8032629 TEST_BUG: Remove RMI tests from exclusiveAccess.dirs
- Closed
-
JDK-8034000 TEST_BUG: lack of /othervm option can cause some RMI tests to fail
- Closed