jshell tests affect command shell windows

[Jan Lahoda]

I guess (a part of) the problem may be tests tweaking the console 
settings and running concurrently (one test changing the console 
settings/changing console to raw; another one running concurrently 
storing these settings, and then the first one ending, followed by the 
second one ending, and actually reseting the console settings to the 
wrong values). So, I guess, the best would be if we avoided setting the 
console to the raw mode during tests (as I don't think we need that anyway):
http://cr.openjdk.java.net/~jlahoda/jshell-test-terminal-change/webrev/

What do you think?

Thanks,
    Jan

On 10.3.2016 01:14, Jonathan Gibbons wrote:
> Linux, Ununtu 14.04.
>
> Vicente reported it on a server, same environment.
>
> -- Jon
>
> On 03/09/2016 02:16 PM, Robert Field wrote:
>> That's not so good (understatement).
>>
>> What platform are you on?
>>
>> -Robert
>>
>> On 03/09/16 13:40, Jonathan Gibbons wrote:
>>> Kulla team,
>>>
>>> Using the latest jdk9/dev bits, if I run the
>>> langtools/test/jdk/jshell tests, my terminal window becomes
>>> corrupted, such that no printable characters are echoed, and "return"
>>> just displays the prompt echaracters repeatedly on the same line.
>>>
>>> A reset command clears the condition, but this is still a pretty
>>> serious problem.
>>>
>>> -- Jon
>>
>