An entry from the nightly analysis report for 2006.03.18:

TESTFAIL:com/sun/jdi/ProcessAttachTest.sh

New JDI_REGRESSION failures (from 2006.03.18)
    com/sun/jdi/ProcessAttachTest.sh
        This test failed due to "RuntimeException: Empty file" on
        Solaris Client VM (machine booberry).
Adding another entry from my nightly analysis report so I
can stop tracking similar failure modes for this test:

New JDI_REGRESSION failures (from 2008.06.30)
* com/sun/jdi/ProcessAttachTest.sh
        This test failed 3 subtests due to:

            Exception in thread "main" java.io.IOException: Bad file number

            Exception in thread "main" java.io.FileNotFoundException:
            /export/local/.../com/sun/jdi/shutdown1.port (No such file
            or directory)

            Exception in thread "main" java.io.FileNotFoundException:
            /export/local/.../com/sun/jdi/shutdown2.port (No such file
            or directory)

        on Solaris SPARC Server VM (machine vm-t1000-03). On Solaris
        SPARC-64 Server VM (machine vm-t1000-01a) only the third
        failure mode occurred.

        This test is covered by the following bug:

            6402201 4/4 ProcessAttachTest.sh needs better synchronization

        The failure mode in the description of 6402201 doesn't match
        these failure modes, but the evaluation of the problem could
        fit.

        Last failure on 2008.11.22 with Linux IA32 Server VM (machine vm-amd64-01), Solaris X86 Server VM (machine julius), Solaris SPARC Client VM (machine denab), Solaris SPARC Server VM (machine vm-t2000-01a), and Solaris SPARC-64 Server VM (machine vm-t1000-04)
        Previous failure on 2008.11.21 with Linux IA32 Server VM (machine maneesha), Solaris X86 Server VM (machine vm-v20z-31), and Solaris SPARC-64 Server VM
(machine jtg-s129)