This test doesn't appear to obtain the PID correctly when working in Cygwin environments, thus causing all JDK8 jobs in JPRT that include the RMI tests to fail. Here is a sample failure:

--------------------------------------------------
TEST: java/rmi/registry/readTest/readTest.sh
JDK under test: (C:\temp\jprt\P2\203840~1.ALB\TESTPR~1\WINDOW~1.2-P)
java version "1.8.0-internal"
Java(TM) SE Runtime Environment (build 1.8.0-internal-201201212038.albatem.jdk-b00)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b10, mixed mode)


ACTION: shell -- Failed. Execution failed: exit code 1
REASON: User specified action: run shell readTest.sh
TIME: 12.797 seconds
messages:
command: shell readTest.sh []
reason: User specified action: run shell readTest.sh
elapsed time (seconds): 12.797
STDOUT:
Test output :
Error: Could not find or load main class readTest
==============
rmiregistry output :
==============
Failed
STDERR:
cp: cannot stat `C:/temp/jprt/P2/203840.albatem/source/test/java/rmi/registry/readTest\\*': No such file or directory
javac: invalid flag: testPkg\*java
Usage: javac <options> <source files>
use -help for a list of possible options
javac: file not found: readTest.java
Usage: javac <options> <source files>
use -help for a list of possible options
/cygdrive/c/temp/jprt/P2/203840.albatem/source/test/java/rmi/registry/readTest/readTest.sh: line 68: kill: (4648) - No such process
/cygdrive/c/temp/jprt/P2/203840.albatem/source/test/java/rmi/registry/readTest/readTest.sh: line 69: 5448 Killed ${TESTJAVA}${FS}bin${FS}rmiregistry 7491 > ..${FS}${RMIREG_OUT} 2>&1 (wd: /cygdrive/c/temp/jprt/P2/203840.albatem/source/build/windows-amd64/testoutput/jdk_rmi/JTwork/java/rmi/registry/readTest/readTest/rmi_tmp)

TEST RESULT: Failed. Execution failed: exit code 1
--------------------------------------------------