Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14855

Make configurable timeout for test StopFromDifferentNodeTestCase

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 24.0.0.Final
    • None
    • Test Suite
    • None

    Description

      On Narayana CI we experience with intermittent failures of the test StopFromDifferentNodeTestCase.

      As the CI is slow we need to be able to configure the timeout for any waiting actions.
      The test waits for the container is stopped
      https://github.com/wildfly/wildfly/blob/master/testsuite/integration/multinode/src/test/java/org/jboss/as/test/multinode/batch/stoprestart/StopFromDifferentNodeTestCase.java#L267
      The delay would be good to be parametrized by timeout adjust parameter.
      https://github.com/wildfly/wildfly-core/blob/16.0.0.Beta4/testsuite/shared/src/main/java/org/jboss/as/test/shared/TimeoutUtil.java

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-13579 Make most of the calls which wait for timeout configurable with TimeoutUtil

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-14828 Add timeout parametrization for multinode DatabaseTimerServiceMultiNodeTestCase

          • 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)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: