During PIT for hs14bo4 2 failures of test 'closed/compiler/6507107/HeapwalkingTest.java' were observed. Links to failures logs:
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-09-06/Main_Baseline_PIT/javase/solaris-sparcv9/server/mixed/javase-solaris-sparcv9_server_mixed_HS_REGRESSION2008-09-07-02-39-22/workDir/closed/compiler/6507107/HeapwalkingTest.jtr

http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-09-06/Main_Baseline_PIT/javase/solaris-amd64/server/comp/javase-solaris-amd64_server_comp_HS_REGRESSION2008-09-07-02-21-34/workDir/closed/compiler/6507107/HeapwalkingTest.jtr

Test consits of 2 java processes: debuggee and debugger, these 2 processes communicate using socket connection. Test failed because of debuggee got ConnectException during connecting to debugger:
debuggee err>>>java.net.ConnectException: Connection refused
debuggee err>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
debuggee err>>> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310)
debuggee err>>> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176)
debuggee err>>> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163)
debuggee err>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:380)
debuggee err>>> at java.net.Socket.connect(Socket.java:569)
debuggee err>>> at java.net.Socket.connect(Socket.java:519)
debuggee err>>> at java.net.Socket.<init>(Socket.java:416)
debuggee err>>> at java.net.Socket.<init>(Socket.java:199)
debuggee err>>> at HeapwalkingTest$IOPipe.<init>(HeapwalkingTest.java:128)

There is race in the test: it is possibile that debuggee will try to create Socket _before_ debugger created ServerSocket, in this case ConnectException is thrown in debuggee, test should handle such cases.