On Tue, 2 Feb 2021 03:57:35 GMT, Prasanta Sadhukhan <psadhuk...@openjdk.org> 
wrote:

>> I do not see a reason to change the test until the root cause of the hang is 
>> not recognized.
>
> There were many instances faced during test sprint where a test was failing 
> in one platform and we added the stability code of waitForIdle,delay etc to 
> make it work. It was not cited as product bug...I believe it's the same 
> here...I am not able to reproduce it locally at all, and I also checked with 
> other who was also not able to reproduce it locally. It  only failed in mach5 
> and it passed once the test is modified with stability fixes...I dont see a 
> reason to stall it.

No this is not the same, this a hang in the product due to failed toolkit 
shutdown, please create one more bug and attach the old test to it reproduce 
the bug.

-------------

PR: https://git.openjdk.java.net/jdk/pull/2220

Reply via email to