Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

https://issues.jboss.org/browse/WFCORE-285 cli tab completion gets confu... #363

Merged
merged 1 commit into from Dec 3, 2014
Merged

https://issues.jboss.org/browse/WFCORE-285 cli tab completion gets confu... #363

merged 1 commit into from Dec 3, 2014

Conversation

aloubyansky
Copy link
Contributor

...sed by double slash

Thanks,
Alexey

@wildfly-ci
Copy link

Linux Build 877 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Core - Full Integration Build 174 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Windows Build 592 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Linux Build 877 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2785, ignored: 58 Build time: 0:20:18

@wildfly-ci
Copy link

Windows Build 592 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2785, ignored: 58 Build time: 0:19:35

@wildfly-ci
Copy link

Core - Full Integration Build 174 outcome was FAILURE using a merge of 3d5111d
Summary: Tests failed: 115 (115 new), passed: 2759, ignored: 305 Build time: 1:00:52

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
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:358)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

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.arquillian.container.test.impl.client.deployment.ClientDeployer.deploy(ClientDeployer.java:89)
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
    at org.jboss.arquillian.container.test.impl.client.deployment.ClientDeployer.undeploy(ClientDeployer.java:128)
    at org.jboss.as.test.clustering.NodeUtil.undeploy(NodeUtil.java:48)

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.arquillian.container.test.impl.client.deployment.ClientDeployer.deploy(ClientDeployer.java:89)
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
    at org.jboss.arquillian.container.test.impl.client.deployment.ClientDeployer.undeploy(ClientDeployer.java:128)
    at org.jboss.as.test.clustering.NodeUtil.undeploy(NodeUtil.java:48)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
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:358)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: 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
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)


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

@wildfly-ci
Copy link

Core - Full Integration Build 182 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Core - Full Integration Build 182 outcome was FAILURE using a merge of 3d5111d
Summary: Tests failed: 97 (2 new), passed: 2794, ignored: 306 Build time: 1:01:06

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice: javax.xml.ws.WebServiceException: Could not send Message.
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:152)

org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not stop container
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
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:358)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.provider.ServiceProviderRegistrationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.dispatcher.CommandDispatcherTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: org.jboss.as.test.clustering.single.web.SimpleWebTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.clustering.single.registry.RegistryTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

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.arquillian.container.test.impl.client.deployment.ClientDeployer.deploy(ClientDeployer.java:89)
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
    at org.jboss.arquillian.container.test.impl.client.deployment.ClientDeployer.undeploy(ClientDeployer.java:128)
    at org.jboss.as.test.clustering.NodeUtil.undeploy(NodeUtil.java:48)

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.arquillian.container.test.impl.client.deployment.ClientDeployer.deploy(ClientDeployer.java:89)
    at org.jboss.as.test.clustering.NodeUtil.deploy(NodeUtil.java:41)

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed: java.lang.IllegalArgumentException: Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
    at org.jboss.arquillian.container.test.impl.client.deployment.ClientDeployer.undeploy(ClientDeployer.java:128)
    at org.jboss.as.test.clustering.NodeUtil.undeploy(NodeUtil.java:48)


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

@wildfly-ci
Copy link

Core - Full Integration Build 183 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Core - Full Integration Build 183 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2949, ignored: 306 Build time: 0:51:55

@bstansberry
Copy link
Contributor

retest this please

@bstansberry
Copy link
Contributor

looks good, but I asked for a retest just in case the above failures were somehow relevant. Very unlikely.

@wildfly-ci
Copy link

Linux Build 897 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Windows Build 609 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Core - Full Integration Build 192 is now running using a merge of 3d5111d

@wildfly-ci
Copy link

Windows Build 609 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2804, ignored: 58 Build time: 0:15:56

@wildfly-ci
Copy link

Linux Build 897 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2804, ignored: 58 Build time: 0:19:36

@wildfly-ci
Copy link

Core - Full Integration Build 192 outcome was SUCCESS using a merge of 3d5111d
Summary: Tests passed: 2949, ignored: 306 Build time: 0:53:59

@bstansberry bstansberry added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Dec 3, 2014
bstansberry added a commit that referenced this pull request Dec 3, 2014
@bstansberry
Merge pull request #363 from aloubyansky/WFCORE-285-doubleslash
74b9dba 
https://issues.jboss.org/browse/WFCORE-285 cli tab completion gets confu...
@bstansberry bstansberry merged commit 74b9dba into wildfly:master Dec 3, 2014
iweiss pushed a commit to iweiss/wildfly-core that referenced this pull request Jun 20, 2017
@bstansberry
Merge pull request wildfly#363 from jurakp/JBEAP-10482
ef8ad3b 
JBEAP-10482 CLI returns always "0" if CLI is started with "cmd /c " on Windows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Milestone
No milestone
3 participants
@aloubyansky @wildfly-ci @bstansberry