On Wed, 17 Mar 2021 19:35:14 GMT, Thomas Stuefe <stu...@openjdk.org> wrote:
>>> The child does no (zero) writes to either stream. It is invoked only to >>> sleep until it is destroyed. >>> The purpose of the test is to verify the exception that is thrown when the >>> other end(child) of the pipe is closed (because the process has been >>> forcibly terminated). >> >> I meant as a consequence of an error. E.g. a crash or a native OOM could >> cause the child to write an error report to stderr. > >> Hmm, maybe the child can create a file to indicate that bootstrap has >> finished. > > Why does the child even have to be a java VM? Its a Java Child for consistency across tests and across OS's. The JavaChild executes a number of specialized commands to consume or provide data to the parent. Piecing that together on different OS's would add more variables to the tests. In this particular case, assuming it's well understood could probably be handled by some native program as long its available on all platforms consistently. ------------- PR: https://git.openjdk.java.net/jdk/pull/3049
