See <
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/2819/changes>
Changes:
[Jason T. Greene] [AS7-4481] Bundle start/stop operation fails silently
[Jason T. Greene] [AS7-4486] Remove feature that starts bundles automatically on
'deploy' operation
[Jason T. Greene] [AS7-4489] BundleContext.ungetService() may lead to ModuleLoadException
[Jason T. Greene] Revisit and cleanup eclipse compiler warnings
[Jason T. Greene] [AS7-4308] FrameworkEvent.STARTED fired before initial set of bundles
are started
[Jason T. Greene] Restore modulesDir from ServerEnvironment in
ModuleIdentityArtifactProvider
[Jason T. Greene] Prepering i18n review - revert to 7.1.1 ids
[Jason T. Greene] [AS7-4543] Allow bundle start/stop operations to work with deploy name
[Jason T. Greene] [JBOSGI-543] Bundle start level not persistently recorded
------------------------------------------
[...truncated 2173 lines...]
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
12:09:01,916 ERROR (main) [org.jboss.as.controller.management-operation]
<AbstractOperationContext.java:418> JBAS014612: Operation ("evil") failed
- address: ([]): java.lang.RuntimeException: this handler is evil
at
org.jboss.as.controller.ModelControllerImplUnitTestCase$ModelStageThrowsExceptionHandler.execute(ModelControllerImplUnitTestCase.java:757)
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466)
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385)
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272)
at
org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
at
org.jboss.as.controller.ModelControllerImplUnitTestCase.testModelStageUnhandledFailureExecution(ModelControllerImplUnitTestCase.java:263)
at
org.jboss.as.controller.ModelControllerImplUnitTestCase.testModelStageUnhandledFailureExecutionNonRecursive(ModelControllerImplUnitTestCase.java:279)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
{
"outcome" => "success",
"result" => 5
}
{
"outcome" => "success",
"result" => 5
}
{
"outcome" => "success",
"result" => 1
}
{
"outcome" => "success",
"result" => 1
}
{
"outcome" => "failed",
"result" => 1,
"rolled-back" => true
}
{
"outcome" => "failed",
"result" => 1,
"rolled-back" => true
}
{
"outcome" => "success",
"result" => 1
}
12:09:02,103 INFO (main) [org.jboss.as.controller] <ContainerStateMonitor.java:185>
JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.depended-service (missing) dependents: [service
jboss.dependent-service]
{
"outcome" => "failed",
"result" => 5,
"failure-description" => "JBAS014762: Removing services has lead to
unsatisfied dependencies:
Service jboss.depended-service was depended upon by service
jboss.dependent-service",
"rolled-back" => true
}
12:09:02,110 INFO (MSC service thread 138-3) [org.jboss.as.controller]
<ContainerStateMonitor.java:185> JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.depended-service (new available)
Tests run: 37, Failures: 0, Errors: 0, Skipped: 5, Time elapsed: 0.895 sec
Running org.jboss.as.controller.operation.validation.ModelTypeValidatorUnitTestCase
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
Running org.jboss.as.controller.ExtensionContextProcessTypeTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Results :
Failed tests:
testBasicMatch(org.jboss.as.controller.interfaces.InetAddressMatchInterfaceCriteriaTestCase):
expected:<1> but was:<0>
Tests run: 231, Failures: 1, Errors: 0, Skipped: 12
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [8.669s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [3.807s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.395s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.908s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [19.205s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [10.404s]
[INFO] JBoss Application Server: Controller Core ......... FAILURE [30.811s]
[INFO] JBoss Application Server: Domain Management ....... SKIPPED
[INFO] JBoss Application Server: Domain HTTP Interface ... SKIPPED
[INFO] JBoss Application Server: Deployment Repository ... SKIPPED
[INFO] JBoss Application Server: Embedded ................ SKIPPED
[INFO] JBoss Application Server: Platform MBean integration SKIPPED
[INFO] JBoss Application Server: Process Controller ...... SKIPPED
[INFO] JBoss Application Server: Network ................. SKIPPED
[INFO] JBoss Application Server: Threading Subsystem ..... SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Server .................. SKIPPED
[INFO] JBoss Application Server: Subsystem Test Harness .. SKIPPED
[INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Naming Subsystem ........ SKIPPED
[INFO] JBoss Application Server: EE ...................... SKIPPED
[INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
[INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
[INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
[INFO] JBoss Application Server: Clustering Server API ... SKIPPED
[INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
[INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
[INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
[INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
[INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
[INFO] JBoss Application Server: Clustered registry service SKIPPED
[INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
[INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
[INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
[INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
[INFO] JBoss Application Server: Config Assembly ......... SKIPPED
[INFO] JBoss Application Server: Command line interface .. SKIPPED
[INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
[INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
[INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider
SKIPPED
[INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
[INFO] JBoss Application Server: Clustered singleton services SKIPPED
[INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
[INFO] JBoss Application Server: Config Admin ............ SKIPPED
[INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
[INFO] JBoss Application Server: EE Deployment ........... SKIPPED
[INFO] JBoss Application Server: JAXR Client ............. SKIPPED
[INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
[INFO] JBoss Application Server: JPA SPI ................. SKIPPED
[INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
[INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Weld Integration ........ SKIPPED
[INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
[INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
[INFO] JBoss Application Server: JDR ..................... SKIPPED
[INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
[INFO] JBoss Application Server: Management Client Content SKIPPED
[INFO] JBoss Application Server: Host Controller ......... SKIPPED
[INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
[INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
[INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
[INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
[INFO] JBoss Application Server: OSGi .................... SKIPPED
[INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
[INFO] JBoss Application Server: OSGi ConfigurationAdmin . SKIPPED
[INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
[INFO] JBoss Application Server: sosreport scripts ....... SKIPPED
[INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
[INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
[INFO] JBoss Application Server: Build ................... SKIPPED
[INFO] JBoss Application Server: Arquillian .............. SKIPPED
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
[INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
[INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
[INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
[INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
[INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
[INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
[INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
[INFO] JBoss Application Server: Distribution ............ SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
[INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs
SKIPPED
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
[INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
[INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
[INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:26.548s
[INFO] Finished at: Mon Apr 23 12:09:02 EDT 2012
[INFO] Final Memory: 123M/477M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test
(default-test) on project jboss-as-controller: There are test failures.
[ERROR]
[ERROR] Please refer to
<
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/controller/target...
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jboss-as-controller
Build step 'Execute shell' marked build as failure
Recording test results
Archiving artifacts