+1
On 5/3/20 10:04 pm, Prasanta Sadhukhan wrote:
That one I added for further safeguard. Anyways, the test is passing now
without the additional delay also. Tested with 100 iterations on mach5 mac (job
details in JBS), so we can just remove from problem List
diff -r 2ec6cfcdfb65 test/jdk/ProblemList.txt
--- a/test/jdk/ProblemList.txtThu Apr 30 22:47:27 2020 +0100
+++ b/test/jdk/ProblemList.txtSat May 02 14:00:42 2020 +0530
@@ -877,7 +877,6 @@
javax/swing/JMenuItem/8139169/ScreenMenuBarInputTwice.java 8233638 macosx-all
javax/swing/JMenuItem/6249972/bug6249972.java 8233640 macosx-all
javax/swing/JMenuItem/4171437/bug4171437.java 8233641 macosx-all
*-javax/swing/JMenuBar/4750590/bug4750590.java 8233642 macosx-all*
javax/swing/JMenu/4692443/bug4692443.java 8171998 macosx-all
javax/swing/JMenu/4515762/bug4515762.java 8233643 macosx-all
javax/swing/JColorChooser/Test8051548.java 8233647 macosx-all
On 04-May-20 4:39 AM, Sergey Bylokhov wrote:
Hi, Prasanta.
On 5/2/20 1:31 am, Prasanta Sadhukhan wrote:
Please review a testbug fix for an issue seen to be failing in macOS nightly
testing.
The test was failing with “Test failed” message on mach5 macOS system primarily
because there was no time gap between component setup and test being executed
on that component.
The test already uses "robo.setAutoDelay(500)" why it does not work? 500 seems
quite big delay.
--
Best regards, Sergey.
