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

javax/management/monitor/AttributeArbitraryDataTypeTest.java timed out

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 18
    • Fix Version/s: tbd
    • Component/s: core-svc

      Description

      The following test timed out the JDK18 CI:

      javax/management/monitor/AttributeArbitraryDataTypeTest.java

      Here's a snippet from the log file:

      #section:main
      ----------messages:(7/290)----------
      command: main AttributeArbitraryDataTypeTest
      reason: User specified action: run main AttributeArbitraryDataTypeTest
      Mode: othervm
      Additional options from @modules: --add-modules java.desktop,java.management
      Timeout information:
      --- Timeout information end.
      elapsed time (seconds): 516.204
      ----------configuration:(3/56)----------
      Boot Layer
        add modules: java.desktop java.management

      ----------System.out:(135/5562)----------
      PDs: 1
      Property: name
      name: do_match_now

      <snip>

      >>> ----------------------------------------
      >>> CREATE a new StringMonitor MBean
      >>> ADD a listener to the StringMonitor
      >>> CREATE a new ObservedObject MBean
      >>> SET the attributes of the StringMonitor:
      ATTRIBUTE "ObservedObject" = DefaultDomain:type=ObservedObject
      ATTRIBUTE "ObservedAttribute" = ComplexAttribute.stringAttribute
      ATTRIBUTE "NotifyMatch" = true
      ATTRIBUTE "NotifyDiffer" = false
      ATTRIBUTE "StringToCompare" = "do_match_now"
      ATTRIBUTE "GranularityPeriod" = 500
      >>> START the StringMonitor
      Timeout refired 480 times
      ----------System.err:(0/0)----------
      ----------rerun:(39/5450)*----------

      <snip>

      result: Error. Program `/opt/mach5/mesos/work_dir/jib-master/install/jdk-18+4-86/linux-aarch64-debug.jdk/jdk-18/fastdebug/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 516193ms).


      The test timed out at 516 seconds and there's no indication that
      the test passed while the timeout handler was running.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dcubed Daniel Daugherty
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: