-
Bug
-
Resolution: Unresolved
-
P4
-
17, 21, 24, 25, 26
-
windows
Test java/awt/dnd/DropActionChangeTest.java times out intermittently on Windows and timeout handling takes 2 hours.
Timeout information:
--- Timeout information end.
finished: Thu Aug 28 14:32:05 GMT 2025
elapsed time (seconds): 7471.833
----------System.out:(1/37)----------
Timeout signalled after 240 seconds
----------System.err:(5/223)----------
DropTargetListener.dragEnter(): user drop action=1
DragSourceListener.dragDropEnd() was not called, returning
STATUS:Passed.
DragSourceListener.dragDropEnd(): drop action=0
FAILURE: wrong drop action:0, It should be 2
The failure has been seen in 17u only, however, I expect it's reproducible in mainline too. We have a few dnd tests failing with similar symptoms where timeout handling takes more than 2 hours. See JDK-8320083, JDK-8316455, JDK-8333091, JDK-8333097, JDK-8224968.
Timeout information:
--- Timeout information end.
finished: Thu Aug 28 14:32:05 GMT 2025
elapsed time (seconds): 7471.833
----------System.out:(1/37)----------
Timeout signalled after 240 seconds
----------System.err:(5/223)----------
DropTargetListener.dragEnter(): user drop action=1
DragSourceListener.dragDropEnd() was not called, returning
STATUS:Passed.
DragSourceListener.dragDropEnd(): drop action=0
FAILURE: wrong drop action:0, It should be 2
The failure has been seen in 17u only, however, I expect it's reproducible in mainline too. We have a few dnd tests failing with similar symptoms where timeout handling takes more than 2 hours. See JDK-8320083, JDK-8316455, JDK-8333091, JDK-8333097, JDK-8224968.
- relates to
-
JDK-8320083 java/awt/dnd/DragTriggerEventTest.java timed out
-
- In Progress
-