Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1237

qa timeout MFACTOR (was: crashrecovery07 tests failing on Solaris11 x86/x86_64 platform)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.6.1.CP14
    • 4.6.1.CP13
    • Testing
    • None

    Description

      When running QA testsuite on Solaris 11 x86/x86_64 platform with Oracle JDK7 I hit intermittent failures at crashrecovery07 tests.

      Affected tests:
      CrashRecovery07_Test04
      CrashRecovery07_Test05
      CrashRecovery07_Test11
      CrashRecovery07_Test12

      output of Test05 (qa/results/113/task_0_out):

      Sleeping for 180000ms.
Test will fail because we have just received value 2 for resource 0
Test will fail because we have just received value 2 for resource 1
Test has failed because we got 2 for 2
Failed

      output of Test11 (qa/results/25/task_0_out):

      Sleeping for 360000ms.
Test will fail because we have just received value 2 for resource 0
Test will fail because we have just received value 2 for resource 1
Test will fail because we have just received value 2 for resource 2
Test has failed because we got 2 for 3
Failed

      Complete logs for the two issues detailed above can be found here:
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBoss%20TS/view/JBossTS-EAP5/job/jbossts-testsuite-solaris-oraclejdk7-eap5/LABEL=sol11_x86_64,jdk=java17_default/1/artifact/sol11_x86_64,java17_default_N1_Thu%20Sep%2006%2001%3A30%3A21%20EDT%202012.zip

      output of Test04 (qa/results/92/task_0_out):

      Sleeping for 450000ms.
Test will fail because we have just received value 2 for resource 0
Test has failed because we got 2 for 1
Failed

      output of Test12 (qa/results/14/task_0_out):

      Sleeping for 450000ms.
Test will fail because we have just received value 2 for resource 0
Test will fail because we have just received value 2 for resource 1
Test will fail because we have just received value 2 for resource 2
Test has failed because we got 2 for 3
Failed

      Complete logs for Test04 and Test12 can be found here:
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBoss%20TS/view/JBossTS-EAP5/job/jbossts-testsuite-solaris-oraclejdk7-eap5/LABEL=sol11_x86,jdk=java17_default/1/artifact/sol11_x86,java17_default_N1_Thu%20Sep%2006%2001%3A30%3A21%20EDT%202012.zip

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-1327 QA Test Suite Failures

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-939 Fix intermittant qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBTM-940 Fix intermittant qa quite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              istudens@redhat.com Ivo Studensky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: