[WFCORE-884] Add a capability for interfaces #963

bstansberry · 2015-08-18T12:42:53Z

Also renames DomainModelReferenceValidator and removes its use from a few cases left over from WFCORE-833.

wildfly-ci · 2015-08-18T12:44:30Z

Linux Build 2402 is now running using a merge of 17e2cca

wildfly-ci · 2015-08-18T13:21:03Z

Linux Build 2402 outcome was SUCCESS using a merge of 17e2cca
Summary: Tests passed: 3401, ignored: 64 Build time: 00:36:34

wildfly-ci · 2015-08-18T13:34:40Z

WildFly pull requests Build 1831 outcome was FAILURE using a merge of 17e2cca
Summary: Snapshot dependency failed: ... WildFly Core Full - Integration Build time: 00:00:07

bstansberry · 2015-08-21T14:48:01Z

Needs wildfly/wildfly#7966 merged. The failing ParseAndMarshalModelsTestCase fails because the test fixture is unable to set up the needed capability. When trying to correct that, I discovered that the tests were fundamentally broken, leading to https://issues.jboss.org/browse/WFLY-5138.

bstansberry · 2015-08-23T19:08:05Z

retest this please

wildfly-ci · 2015-08-23T19:09:44Z

Core - Full Integration Build 3 is now running using a merge of 7378b87

wildfly-ci · 2015-08-23T19:09:46Z

Linux Build 2457 is now running using a merge of 7378b87

wildfly-ci · 2015-08-23T19:12:15Z

Core - Full Integration Build 3 outcome was FAILURE using a merge of 8901c8d
Summary: Exit code 1 Build time: 00:02:34

wildfly-ci · 2015-08-23T19:46:56Z

Linux Build 2457 outcome was SUCCESS using a merge of 8901c8d
Summary: Tests passed: 3402, ignored: 64 Build time: 00:37:14

wildfly-ci · 2015-08-23T19:59:02Z

WildFly pull requests Build 1878 outcome was FAILURE using a merge of 8901c8d
Summary: Snapshot dependencies failed: 2 (new) Build time: 00:00:08

wildfly-ci · 2015-08-23T19:59:52Z

Linux Build 2458 is now running using a merge of 8901c8d

wildfly-ci · 2015-08-23T19:59:52Z

Core - Full Integration Build 4 is now running using a merge of 8901c8d

wildfly-ci · 2015-08-23T20:02:15Z

Core - Full Integration Build 4 outcome was FAILURE using a merge of 8901c8d
Summary: Exit code 1 Build time: 00:02:26

wildfly-ci · 2015-08-23T20:36:38Z

Linux Build 2458 outcome was SUCCESS using a merge of 8901c8d
Summary: Tests passed: 3402, ignored: 64 Build time: 00:36:49

wildfly-ci · 2015-08-23T20:48:29Z

WildFly pull requests Build 1880 outcome was FAILURE using a merge of 8901c8d
Summary: Snapshot dependencies failed: 2 Build time: 00:00:02

Also renames DomainModelReferenceValidator and removes its use from a few cases left over from WFCORE-833.

wildfly-ci · 2015-08-27T14:24:52Z

Linux Build 2511 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T14:24:52Z

Windows Build 2022 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T14:24:53Z

Core - Full Integration Build 1638 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T14:25:27Z

Core - Full Integration - Windows Build 59 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T15:02:53Z

Linux Build 2511 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3402, ignored: 64 Build time: 00:38:01

wildfly-ci · 2015-08-27T15:21:17Z

Core - Full Integration Build 1638 outcome was FAILURE using a merge of c2c98a1
Summary: Tests failed: 136 (136 new), passed: 2803, ignored: 358 Build time: 00:56:26

Failed tests

org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.registry.RegistryTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredQueue: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.setUp(ClusteredMessagingTestCase.java:89)
------- Stdout: -------


org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.testClusteredTopic: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.messaging.ClusteredMessagingTestCase.setUp(ClusteredMessagingTestCase.java:89)
------- Stdout: -------


org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.deploy(ClusterAbstractTestCase.java:115)
    at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:37)
------- Stdout: -------
17:16:04,129 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) xsite.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet$Custom.class
/WEB-INF/web.xml
/META-INF/
/META-INF/MANIFEST.MF
17:16:04,143 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) xsite.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet$Custom.class
/WEB-INF/web.xml
/META-INF/
/META-INF/MANIFEST.MF
17:16:04,149 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) xsite.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/org/
/WEB-INF/classes/org/jboss/
/WEB-INF/classes/org/jboss/as/
/WEB-INF/classes/org/jboss/as/test/
/WEB-INF/classes/org/jboss/as/test/clustering/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet.class
/WEB-INF/classes/org/jboss/as/test/clustering/xsite/CacheAccessServlet$Custom.class
/WEB-INF/web.xml
/META-INF/
/META-INF/MANIFEST.MF
17:16:04,152 INFO  [org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase] (main) xsite.war:
/WEB-INF/
/WEB-INF/classes/
/WEB-INF/classes/org/


org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.deploy(ClusterAbstractTestCase.java:115)
    at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:37)
------- Stdout: -------
17:16:22,223 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)
    at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:68)
    at org.jboss.as.test.clustering.cluster.ClusterAbstractTestCase.start(ClusterAbstractTestCase.java:107)
    at org.jboss.as.test.clustering.cluster.ExtendedClusterAbstractTestCase.beforeTestMethod(ExtendedClusterAbstractTestCase.java:36)

17:16:22,279 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
17:16:22,280 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-2
17:16:22,280 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-3
17:16:22,281 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0


org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)


org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:309)
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:80)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:110)



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

wildfly-ci · 2015-08-27T15:23:47Z

Core - Full Integration - Windows Build 59 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3056, ignored: 358 Build time: 00:58:21

wildfly-ci · 2015-08-27T15:25:05Z

Windows Build 2022 outcome was FAILURE using a merge of c2c98a1
Summary: Execution timeout (new); tests passed: 3048, ignored: 50 Build time: 01:00:13

jamezp · 2015-08-27T18:12:08Z

retest this please

wildfly-ci · 2015-08-27T18:14:54Z

Core - Full Integration Build 1641 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T18:14:54Z

Linux Build 2514 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T18:14:54Z

Windows Build 2025 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T18:14:54Z

Core - Full Integration - Windows Build 62 is now running using a merge of c2c98a1

wildfly-ci · 2015-08-27T18:50:15Z

Windows Build 2025 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3403, ignored: 64 Build time: 00:35:23

wildfly-ci · 2015-08-27T18:50:40Z

Linux Build 2514 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3403, ignored: 64 Build time: 00:35:47

wildfly-ci · 2015-08-27T19:04:12Z

Core - Full Integration Build 1641 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3056, ignored: 358 Build time: 00:49:19

wildfly-ci · 2015-08-27T19:05:20Z

Core - Full Integration - Windows Build 62 outcome was SUCCESS using a merge of c2c98a1
Summary: Tests passed: 3056, ignored: 358 Build time: 00:50:27

[WFCORE-884] Add a capability for interfaces

bstansberry added the fixme This PR introduces issues that must be fixed label Aug 18, 2015

bstansberry added downstream-update-required and removed fixme This PR introduces issues that must be fixed downstream-update-required labels Aug 21, 2015

bstansberry force-pushed the WFCORE-884 branch from 17e2cca to 7378b87 Compare August 23, 2015 19:08

bstansberry force-pushed the WFCORE-884 branch from 7378b87 to 8901c8d Compare August 23, 2015 19:10

[WFCORE-884] Add a capability for interfaces

c2c98a1

Also renames DomainModelReferenceValidator and removes its use from a few cases left over from WFCORE-833.

bstansberry force-pushed the WFCORE-884 branch from 8901c8d to c2c98a1 Compare August 27, 2015 14:24

jamezp added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Aug 27, 2015

jamezp added a commit to jamezp/wildfly-core that referenced this pull request Aug 27, 2015

Merged pull request wildfly#963

e113906

[WFCORE-884] Add a capability for interfaces

jamezp added a commit that referenced this pull request Aug 28, 2015

Merge pull request #963 from bstansberry/WFCORE-884

43af227

[WFCORE-884] Add a capability for interfaces

jamezp merged commit 43af227 into wildfly:master Aug 28, 2015

bstansberry deleted the WFCORE-884 branch August 30, 2015 20:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[WFCORE-884] Add a capability for interfaces #963

[WFCORE-884] Add a capability for interfaces #963

bstansberry commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

bstansberry commented Aug 21, 2015

bstansberry commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

jamezp commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

[WFCORE-884] Add a capability for interfaces #963

[WFCORE-884] Add a capability for interfaces #963

Conversation

bstansberry commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

wildfly-ci commented Aug 18, 2015

bstansberry commented Aug 21, 2015

bstansberry commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 23, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

Failed tests

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

jamezp commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015

wildfly-ci commented Aug 27, 2015