Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-5074607

regression test javax/swing/JTabbedPane/4680657/Bug4680657.java failed



    • Subcomponent:
    • CPU:
    • OS:


      JDK: /net/jano/export/disk12/i18n/NightlyBuilds/archives/2004-07-14.tiger

      System: Solaris Sparc 10, b61; RedHat AS 3.0

      Testcase: test/javax/swing/JTabbedPane/4680657/Bug4680657.java

      Test failed with the following exceptions:

        right-to-left: <Metal> LEFT Expected:0 1 2 3 4, Got:0 0 0 0 0
        right-to-left: <Metal> BOTTOM Expected:0 1 2 3 4, Got:0 0 0 0 0
        right-to-left: <Metal> RIGHT Expected:0 1 2 3 4, Got:0 0 0 0 0
        right-to-left: <Metal> TOP Expected:0 1 2 3 4, Got:0 0 0 0 0
      java.lang.RuntimeException: Wrong Focus Movement
              at Bug4680657.test(Bug4680657.java:70)
              at Bug4680657.main(Bug4680657.java:17)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:582)
              at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
              at java.lang.Thread.run(Thread.java:595)

      JavaTest Message: Test threw exception: java.lang.RuntimeException: Wrong Focus Movement
      JavaTest Message: shutting down test


      The failure is not PIT specific, it also failed in previous builds.

      ###@###.### 2004-07-15

      When ran the failed test alone, it passed on both RHAS 3.0 and Solaris 10 - the same machines that test failed.

      ... the test actually failed in few of DTF nightly test run,
      in more than one configurations,..
      All the machines when running the regression test, shouldn't have other
      programs running, and those nightly test mostly running on 3rd floor lab
      during the night, I wouldn't think anyone would touch machines; but most
      of DTF machines are kind of slow, it might be timing issue?

      > If possible, could you please modify the test program and run it with
      > DTF on the machines when you have time?
      > The test program includes some delay(), but I think that it may be too
      > short on some machines.
      > Could you please change values for all of delay()s and run it?
      > For example,
      > robot.delay(1000); -> robot.delay(10000);
      > robot.delay(500); -> robot.delay(5000);
      > robot.delay(300); -> robot.delay(3000);
      > robot.delay(300); -> robot.delay(3000);
      > robot.delay(300); -> robot.delay(3000);
      > If the test passes with this change, we'll be able to finish working
      > on this bug soon. Bingo! If it fails, we need to investigate more....

      I did run the tests with the above modification in DTF, and the test still failed.

      One of test result can be found at

      ###@###.### 2004-08-13

      Tested with mustang b73, the failure is no longer reproducible.
      Closing as not reproducible...




            mtiensunw Minchi Tien (Inactive)
            mtiensunw Minchi Tien (Inactive)
            0 Vote for this issue
            0 Start watching this issue