<AWT Dev>  Review Request for several test bugs: 8150535, 8151033, 8151037 etc.
yuri.nesterenko at oracle.com
Tue Mar 29 09:47:31 UTC 2016
(see also my answer in
Unfortunately, this changeset is already pushed.
Generally, some of the tests is not hard to adapt for non-modules
execution mode, and let's try that sometimes, however
(1) some of them already run well with jdk8 (bug8133039.java,
(2) there's no way back from Jigsaw; with time, that conditional
execution would introduce unnecessary complexity
(WrappedToolkitTest.sh would be two times bigger, why not use
(3) Some of the tests is not easy to make two-way even now:
for instance, every test requiring Xpatch.
Thank you! In future I will have in mind that getLocation()
On 03/29/2016 10:49 AM, Semyon Sadetsky wrote:
> Hi Yuri,
> Is it possible to make those tests to run on both Jigsaw and non-Jigsaw
> Some tests may be unstable on Ubuntu because of
> To make stability better I propose to replace all top windows
> getLocation() by getLocationOnScreen() and for rectangles got by
> getBounds() to call setLocation(window.getLocationOnScreen()).
> getLocationOnScreen() queries the position from WM directly and is more
> On 3/24/2016 6:12 PM, Yuri Nesterenko wrote:
>> Sergey, I'm sorry,
>> filing JDK-8152693, I found an error in that version.
>> A new one is
>> The spawned processes were provided with addExports.
>> Shame on me!
>> On 03/24/2016 05:34 PM, Sergey Bylokhov wrote:
>>> cc swing-dev
>>> On 24.03.16 17:17, Yuri Nesterenko wrote:
>>>> please review this test-only fix, a leftover from Jigsaw M3
>>>> Some 7 tests fixed but note that not all of them always pass even
>>>> I need to file a bug about the fixed here manual test
>>>> Thank you!
More information about the awt-dev