See bug 6221549.
The original problem in 6221549 was fixed in both mustang and tiger.
Subsequently, and additional instance of this failure was found on certain fast amd64 processors running Solaris or Linux.
The cause of the second instance was exiting the JVM before the success reporting strings were outputed to the port being monitored by the TCK harnes.
This was fixed in mustang by adding additional Trace.flush(); ststement to the end of Main.tckprintln().