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

sajdi tests timeout on slow machines

    Details

    • Subcomponent:
      svc
    • CPU:
      generic
    • OS:
      generic

      Description

      Here is an entry from my nightly analysis report:

      nsk.sajdi
         nsk/sajdi/jdb/options/connect/connect003
         nsk/sajdi/jdb/options/connect/connect004
              2009.03.11 Solaris SPARC Server VM -Xcomp (machine carrot, DebugServer)
              2009.03.06 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)
              2009.03.03 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)

         nsk/sajdi/SADebugServerAttachingConnector/attach/attach001
         nsk/sajdi/SADebugServerAttachingConnector/attach/attach002
         nsk/sajdi/SADebugServerAttachingConnector/attach/attach011
              2009.03.11 Solaris SPARC Server VM -Xcomp (machine carrot, DebugServer)
              2009.03.09 Solaris SPARC Server VM -Xcomp (machine vm-t2000-01b, DebugServer)
              2009.03.06 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)
              2009.03.03 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)

          nsk/sajdi/SADebugServerAttachingConnector/attach/attach012
              2009.03.09 Solaris SPARC Server VM -Xcomp (machine vm-t2000-01b, DebugServer)
              2009.03.06 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)
              2009.03.03 Solaris SPARC-64 Server VM -Xcomp (machine jtg-s111, DebugServer)


      Here is the link to the analysis page:

      http://sqeweb.sfbay/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-03-11/RT_Baseline/vm/solaris-sparc/server/comp/solaris-sparc_server_comp_nsk.sajdi.testlist/analysis.html

      Here are snippets from the .log file:


      [2009-03-12T04:59:10.13] script> - not ready: 45 seconds
      [2009-03-12T04:59:10.13] script> - not ready: 50 seconds
      [2009-03-12T04:59:10.13] Debuggee class started
      [2009-03-12T04:59:10.13] Debuggee class ready for debugging
      [2009-03-12T04:59:10.13] script> - not ready: 55 seconds
      [2009-03-12T04:59:10.13] DEBUGGEE_READY_FOR_DEBUGGING
      [2009-03-12T04:59:10.13] script> Debuggee VM got ready for debugging

      <snip>


      [2009-03-12T04:59:40.69] script> Wait for DebugServer to become ready within timeout: 300 seconds
      [2009-03-12T04:59:40.69] script> - not ready: 0 seconds
      [2009-03-12T04:59:40.69] script> - not ready: 5 seconds
      <snip>
      [2009-03-12T05:04:14.68] script> - not ready: 290 seconds
      [2009-03-12T05:04:14.68] script> - not ready: 295 seconds
      [2009-03-12T05:04:14.68] script> # ERROR: DebugServer has not become ready for timeout: 300 seconds
      [2009-03-12T05:04:14.68] script> DebugServer output:
      [2009-03-12T05:04:14.68] Attaching to process ID 8913 and starting RMI services, please wait...
      [2009-03-12T05:04:14.68] Debugger attached and RMI services started.
      [2009-03-12T05:04:14.68] script>
      [2009-03-12T05:04:14.68] script> Kill DebugServer and rmiregistry processes by pid: 9039
      [2009-03-12T05:04:14.96] script> Kill rmiregistry process by pid: 9038
      [2009-03-12T05:04:14.96] script> Kill debuggee VM processes by pid: 8913
      [2009-03-12T05:04:14.96] # Test level exit status: 97


      It looks like the DebugServer process got ready right at the
      300 second timeout. That's five minutes for the DebugServer
      process to get up and running. Ouch...

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: