WFLY-436 Inline JGroups subsystem references to threads subsystem #6952

rhusar · 2014-11-14T01:58:26Z

Jira:
https://issues.jboss.org/browse/WFLY-436

wildfly-ci · 2014-11-14T02:05:12Z

Linux with security manager Build 463 is now running using a merge of 87e9ff3

wildfly-ci · 2014-11-14T02:05:12Z

Linux Build 5474 is now running using a merge of 87e9ff3

wildfly-ci · 2014-11-14T02:05:13Z

Windows Build 577 is now running using a merge of 87e9ff3

wildfly-ci · 2014-11-14T02:12:09Z

Linux with security manager Build 463 outcome was FAILURE using a merge of 87e9ff3
Summary: Tests failed: 18 (18 new), passed: 780, ignored: 245 Build time: 0:06:57

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostMaster: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHost: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostSlave: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalonePicketLink: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 8 more failed tests, see build details

wildfly-ci · 2014-11-14T02:56:38Z

Windows Build 577 outcome was FAILURE using a merge of c5a980e
Summary: Tests failed: 18 (18 new), passed: 2983, ignored: 238, muted: 1 Build time: 0:51:27

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostMaster: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHost: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostSlave: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalonePicketLink: java.lang.AssertionError: 249:104 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 8 more failed tests, see build details

rhusar · 2014-11-14T02:57:38Z

Retest this please.

wildfly-ci · 2014-11-14T02:58:13Z

Linux Build 5474 outcome was FAILURE using a merge of c5a980e
Summary: Tests failed: 18 (18 new), passed: 2983, ignored: 238, muted: 1 Build time: 0:53:01

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostMaster: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHost: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostSlave: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalonePicketLink: java.lang.AssertionError: 249:104 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd' src-resolve.4.1: Error resolving component 'time-unitType'. It was detected that 'time-unitType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. If 'time-unitType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'time-unitType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/../../../dist/target/wildfly-9.0.0.Alpha2-SNAPSHOT/docs/schema/jboss-as-jgroups_3_0.xsd'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 8 more failed tests, see build details

wildfly-ci · 2014-11-14T03:00:13Z

Linux with security manager Build 465 is now running using a merge of c5a980e

wildfly-ci · 2014-11-14T03:00:13Z

Linux Build 5476 is now running using a merge of c5a980e

wildfly-ci · 2014-11-14T03:00:14Z

Windows Build 579 is now running using a merge of c5a980e

wildfly-ci · 2014-11-14T03:06:37Z

Linux with security manager Build 465 outcome was SUCCESS using a merge of c5a980e
Summary: Tests passed: 798, ignored: 245 Build time: 0:06:24

wildfly-ci · 2014-11-14T03:51:22Z

Windows Build 579 outcome was SUCCESS using a merge of c5a980e
Summary: Tests passed: 3002, ignored: 238, muted: 1 Build time: 0:51:09

wildfly-ci · 2014-11-14T03:53:52Z

Linux Build 5476 outcome was SUCCESS using a merge of c5a980e
Summary: Tests passed: 3003, ignored: 238 Build time: 0:53:40

ctomc · 2014-11-14T10:55:06Z

...ng/jgroups/src/main/java/org/jboss/as/clustering/jgroups/subsystem/ThreadPoolDefinition.java

+ * @author Radoslav Husar
+ * @version Aug 2014
+ */
+public class ThreadPoolDefinition extends SimpleResourceDefinition {


Why not use one of *ThreadPoolResourceDefinition already defined in threads subsystem?

Because we plan to parameterize the default attribute values for each jgroups use case (i.e. internal, default, OOB, and timer thread pools).

pferraro · 2014-11-21T14:33:01Z

FYI - I've made some enhancements, including parameterized default values for thread pool attributes, here:
rhusar#4

rhusar · 2014-12-08T14:00:27Z

Retest this please.

wildfly-ci · 2014-12-08T14:01:26Z

Linux with security manager Build 617 is now running using a merge of a327c6a

wildfly-ci · 2014-12-08T14:01:27Z

Linux Build 5631 is now running using a merge of a327c6a

wildfly-ci · 2014-12-08T14:01:28Z

Windows Build 743 is now running using a merge of a327c6a

wildfly-ci · 2014-12-08T14:07:03Z

Linux with security manager Build 617 outcome was SUCCESS using a merge of a327c6a
Summary: Tests passed: 797, ignored: 370 Build time: 0:05:36

wildfly-ci · 2014-12-08T14:52:11Z

Windows Build 743 outcome was SUCCESS using a merge of a327c6a
Summary: Tests passed: 3017, ignored: 365 Build time: 0:50:45

wildfly-ci · 2014-12-08T14:56:12Z

Linux Build 5631 outcome was FAILURE using a merge of a327c6a
Summary: Tests failed: 1 (1 new), passed: 3016, ignored: 365 Build time: 0:54:46

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: java.lang.reflect.UndeclaredThrowableException: null
    at com.sun.proxy.$Proxy61.runTestMethod(Unknown Source)
    at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:71)

rhusar · 2014-12-11T14:57:28Z

Retest this please (unrelated failure).

wildfly-ci · 2014-12-11T15:00:49Z

Linux Build 5649 is now running using a merge of a327c6a

wildfly-ci · 2014-12-11T15:00:50Z

Linux with security manager Build 634 is now running using a merge of a327c6a

wildfly-ci · 2014-12-11T15:00:50Z

Windows Build 760 is now running using a merge of a327c6a

wildfly-ci · 2015-02-24T20:35:36Z

Linux Build 5953 is now running using a merge of f0df325

wildfly-ci · 2015-02-24T20:35:36Z

Linux with security manager Build 932 is now running using a merge of f0df325

wildfly-ci · 2015-02-24T20:35:37Z

Windows Build 1063 is now running using a merge of f0df325

wildfly-ci · 2015-02-24T20:40:38Z

Linux with security manager Build 932 outcome was SUCCESS using a merge of f0df325
Summary: Tests passed: 840, ignored: 319 Build time: 0:05:02

wildfly-ci · 2015-02-24T21:22:11Z

Linux Build 5953 outcome was SUCCESS using a merge of f0df325
Summary: Tests passed: 2927, ignored: 313, muted: 1 Build time: 0:46:35

wildfly-ci · 2015-02-24T21:22:46Z

Windows Build 1063 outcome was FAILURE using a merge of f0df325
Summary: Tests failed: 1 (1 new), passed: 2927, ignored: 313 Build time: 0:47:10

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: expected:<200> but was:<500>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:743)

rhusar · 2015-02-25T08:16:16Z

Retest this please.

wildfly-ci · 2015-02-25T08:20:16Z

Windows Build 1066 is now running using a merge of f0df325

wildfly-ci · 2015-02-25T08:20:16Z

Linux with security manager Build 935 is now running using a merge of f0df325

wildfly-ci · 2015-02-25T08:20:16Z

Linux Build 5956 is now running using a merge of f0df325

wildfly-ci · 2015-02-25T08:26:45Z

Linux with security manager Build 935 outcome was SUCCESS using a merge of f0df325
Summary: Tests passed: 840, ignored: 319 Build time: 0:06:29

wildfly-ci · 2015-02-25T09:06:47Z

Windows Build 1066 outcome was SUCCESS using a merge of f0df325
Summary: Tests passed: 2928, ignored: 313 Build time: 0:46:32

wildfly-ci · 2015-02-25T09:07:25Z

Linux Build 5956 outcome was SUCCESS using a merge of f0df325
Summary: Tests passed: 2928, ignored: 313 Build time: 0:47:09

Delegate thread pool configuration directly to JGroups Parameterize default values for thread pool attribute definitions

…el; XSD fix

…rrency subsystem way

wildfly-ci · 2015-02-25T09:40:35Z

Linux Build 5957 is now running using a merge of 0168c48

wildfly-ci · 2015-02-25T09:40:35Z

Linux with security manager Build 936 is now running using a merge of 0168c48

wildfly-ci · 2015-02-25T09:40:36Z

Windows Build 1067 is now running using a merge of 0168c48

wildfly-ci · 2015-02-25T09:45:58Z

Linux with security manager Build 936 outcome was SUCCESS using a merge of 0168c48
Summary: Tests passed: 840, ignored: 319 Build time: 0:05:23

wildfly-ci · 2015-02-25T10:27:27Z

Windows Build 1067 outcome was SUCCESS using a merge of 0168c48
Summary: Tests passed: 2928, ignored: 313 Build time: 0:46:52

wildfly-ci · 2015-02-25T10:27:58Z

Linux Build 5957 outcome was SUCCESS using a merge of 0168c48
Summary: Tests passed: 2928, ignored: 313 Build time: 0:47:24

WFLY-436 Inline JGroups subsystem references to threads subsystem

ctomc · 2015-02-25T17:58:28Z

woohoo! now we can "remove" threads subsystem :)

rhusar · 2015-02-25T18:31:37Z

@ctomc Sorry, not so fast...! still working on the last Infinispan part.

rhusar force-pushed the WFLY-436 branch from 87e9ff3 to c5a980e Compare November 14, 2014 02:29

ctomc reviewed Nov 14, 2014
View reviewed changes

rhusar force-pushed the WFLY-436 branch from 7d553e6 to f0df325 Compare February 24, 2015 20:34

rhusar added 4 commits February 25, 2015 10:37

WFLY-436 Inline JGroups subsystem references to threads subsystem

d0f988a

Delegate thread pool configuration directly to JGroups Parameterize default values for thread pool attribute definitions

Make AbstractProtocolConfigurationBuilder a usable builder

84b78bb

WFLY-436 Always apply JGroups thread configuration defined by the mod…

2a1c0a0

…el; XSD fix

WFLY-436 Remove option to specify keepalive time unit; adopt ee concu…

0168c48

…rrency subsystem way

rhusar force-pushed the WFLY-436 branch from f0df325 to 0168c48 Compare February 25, 2015 09:39

bstansberry added a commit that referenced this pull request Feb 25, 2015

Merge pull request #6952 from rhusar/WFLY-436

aa311a8

WFLY-436 Inline JGroups subsystem references to threads subsystem

bstansberry merged commit aa311a8 into wildfly:master Feb 25, 2015

rhusar deleted the WFLY-436 branch February 25, 2015 15:04

WFLY-436 Inline JGroups subsystem references to threads subsystem #6952

WFLY-436 Inline JGroups subsystem references to threads subsystem #6952

Conversation

rhusar commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

Build problems:

Failed tests

wildfly-ci commented Nov 14, 2014

Build problems:

Failed tests

rhusar commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

Build problems:

Failed tests

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

wildfly-ci commented Nov 14, 2014

ctomc Nov 14, 2014

Choose a reason for hiding this comment

pferraro Nov 19, 2014

Choose a reason for hiding this comment

pferraro commented Nov 21, 2014

rhusar commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

wildfly-ci commented Dec 8, 2014

Build problems:

Failed tests

rhusar commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Feb 24, 2015

wildfly-ci commented Feb 24, 2015

wildfly-ci commented Feb 24, 2015

wildfly-ci commented Feb 24, 2015

wildfly-ci commented Feb 24, 2015

wildfly-ci commented Feb 24, 2015

Build problems:

Failed tests

rhusar commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

wildfly-ci commented Feb 25, 2015

ctomc commented Feb 25, 2015

rhusar commented Feb 25, 2015