<AWT Dev> <Swing Dev> [11] Review Request: 8199022 New

Krishna Addepalli krishna.addepalli at oracle.com
Thu Mar 8 11:03:00 UTC 2018

Hi Sergey, 

Bug id is JDK-8197798 for java/awt/JAWT/JAWT.sh


Message: 1
Date: Wed, 7 Mar 2018 05:55:58 -0800
From: Sergey Bylokhov <Sergey.Bylokhov at oracle.com>
To: Prasanta Sadhukhan <prasanta.sadhukhan at oracle.com>,
	"swing-dev at openjdk.java.net" <swing-dev at openjdk.java.net>,
	"awt-dev at openjdk.java.net" <awt-dev at openjdk.java.net>
Subject: Re: <AWT Dev> <Swing Dev> [11] Review Request: 8199022 New
	failures should be added to ProblemList
Message-ID: <b472fe19-4771-7b98-b189-b1cbcabc7916 at oracle.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi, Prasanta.
What bugid for java/awt/JAWT/JAWT.sh ?

On 07/03/2018 00:21, Prasanta Sadhukhan wrote:
> Hi Sergey,
> Looks ok to me. Could you also please add these tests to the list as 
> well
> java/awt/image/VolatileImage/CustomCompositeTest.java 8199002 
> windows-all, linux-all 
> java/awt/image/VolatileImage/GradientPaints.java 8199003 linux-all 
> java/awt/JAWT/JAWT.sh?? windows-all
> Regards
> Prasanta
> On 3/7/2018 5:47 AM, Sergey Bylokhov wrote:
>> Hello.
>> Please review an update of the ProblemList for jdk11.
>> The goal is to make our testing as stable as possible and exclude any 
>> unstable tests(I have started from the tests which may be run in the 
>> headless mode).
>> In this iteration I have updated the problemList for tests which were 
>> failed in our nightly at least once for last week. I tested this fix 
>> in mach5 seven times and always got a green status for open tests.
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8199022
>> Webrev can be found at: 
>> http://cr.openjdk.java.net/~serb/8199022/webrev.00/
>> ?- The ProblemList.txt is updated, I have created a list of new bugs 
>> for the tests which fail at least once in a few iterations on a 
>> different systems.
>> ?- The TEST.ROOT is updated, because "javax/swing" was missed when it 
>> was updated last time in JDK-8002120. The reason is that our tests 
>> does not work well in the agentvm mode(they affects each other in 
>> some unclear way which is reproduced in nightly only).

Best regards, Sergey.

More information about the awt-dev mailing list