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

Clustering integration tests fails once -Dnode0 and -Dnode1 are used

XMLWordPrintable

    • Hide

      ./integration-tests.sh clean install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.*.* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

      Show
      ./integration-tests.sh clean install -Dmaven.repo.local=$MAVEN_REPO_LOCAL -Dmcast=$MCAST_ADDR -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.*.* -Djboss.dist=$JBOSS_DIST -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

      Tests from wildfly-ts-integ-clustering module fails once we change default binding interfaces by -Dnode0 and -Dnode1 properties.

      See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-as-testsuite-clustering/

      • build 5 binds to localhost (no -Dnode*)
      • build 6 uses -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

      Similar failures were addressed for EAP 6 by https://bugzilla.redhat.com/show_bug.cgi?id=1076015

        1. results.zip
          195 kB
        2. testsuite.clustering.logs.zip
          444 kB
        3. maven.logs
          2.60 MB

              rhn-engineering-rhusar Radoslav Husar
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: