BTW, this CR is still covering the kill002 failure, so you need to
either include a fix for it also, or create a separate CR for it. I
think a separate CR would be best because it is a different root cause.
Chris
On 9/20/18 2:47 PM, Chris Plummer wrote:
Looks good. Still not bullet proof, but I'm not sure it's possible to
write tests like this in a way that will work no matter what output is
produced by the method enter/exit events.
Chris
On 9/20/18 10:59 AM, Gary Adams wrote:
The test failure has been identified due to the "int[2]"
being misrecognized as a compound prompt. This caused a cont
command to be sent prematurely.
The proposed fix waits for the correct prompt before
advancing to the next command.
Webrev: http://cr.openjdk.java.net/~gadams/8208473/webrev/
Issue: https://bugs.openjdk.java.net/browse/JDK-8208473
Testing is in progress.
