Details
-
Bug
-
Resolution: Fixed
-
P4
-
8, 11, 17, 19, 20
-
None
-
b21
-
os_x
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8288956 | 17.0.5 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8295202 | 11.0.18 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
Description
JDK 8 b117
Test test/java/awt/dnd/DropTargetEnterExitTest/MissedDragExitTest.java failed
Exception in thread "main" java.lang.RuntimeException: Failed. Drag exit was not called
at MissedDragExitTest.main(MissedDragExitTest.java:107)
Java Result: 1
Seems the Util.waitForIdle() does not work as expected.
Util.drag(r,
new Point(FRAME_LOCATION + FRAME_SIZE / 3, FRAME_LOCATION + FRAME_SIZE / 3),
new Point(FRAME_LOCATION + FRAME_SIZE / 3 *2 , FRAME_LOCATION + FRAME_SIZE / 3 *2),
InputEvent.BUTTON1_MASK);
Util.waitForIdle(r);
if (!dragExitCalled) {
throw new RuntimeException("Failed. Drag exit was not called" );
}
After starting Util.drag() there is a call of Util.waitForIdle() method.
But actually main thread does not wait for idling robot thread. It immediately verifies dragExitCalled propperty, that is still false.
If set shorter track for mouse dragging (like 5 pixels), dragExitCalled has time for changing it state, and entire test passes.
Attachments
Issue Links
- backported by
-
JDK-8288956 [TEST_BUG] [macosx] java/awt/dnd/DropTargetEnterExitTest/MissedDragExitTest.java failed
- Resolved
-
JDK-8295202 [TEST_BUG] [macosx] java/awt/dnd/DropTargetEnterExitTest/MissedDragExitTest.java failed
- Resolved
- relates to
-
JDK-8274597 Some of the dnd tests time out and fail intermittently
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/c064dcea
-
Commit openjdk/jdk17u-dev/9f570189
-
Commit openjdk/jdk/669ac611
-
Review openjdk/jdk11u-dev/1437
-
Review openjdk/jdk17u-dev/483
-
Review openjdk/jdk/8316