[weld-issues] [JBoss JIRA] Resolved: (WELD-651) Functional tests for clustered numberguess application do not work
Martin Gencur (JIRA)
jira-events at lists.jboss.org
Thu Sep 16 03:24:28 EDT 2010
[ https://jira.jboss.org/browse/WELD-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Gencur resolved WELD-651.
--------------------------------
Resolution: Done
Fixed.
> Functional tests for clustered numberguess application do not work
> ------------------------------------------------------------------
>
> Key: WELD-651
> URL: https://jira.jboss.org/browse/WELD-651
> Project: Weld
> Issue Type: Bug
> Components: Examples, Testing Infrastructure (Mocks and Harness Integration)
> Affects Versions: 1.1.0.Beta1
> Reporter: Jozef Hartinger
> Assignee: Martin Gencur
>
> Firstly, the readme says to use "ftest-jboss-cluster-60" profile. The profile is actually "ftest-jboss-cluster-6"
> The test then fails with the following exception. Note that the application is succesfully deployed and working in a cluster.
> Launching Selenium Server
> Waiting for Selenium Server...
> [INFO] Redirecting output to: /home/jharting/jboss/testing/Weld-1.1.0.Beta1/weld-1.1.0.Beta1/examples/jsf/numberguess/target/ftest-logs/selenium-server.log
> [INFO] User extensions: /home/jharting/jboss/testing/Weld-1.1.0.Beta1/weld-1.1.0.Beta1/examples/jsf/numberguess/target/selenium/user-extensions.js
> Selenium Server started
> [INFO]
> [INFO] --- maven-antrun-plugin:1.3:run (farm-example) @ weld-jsf-numberguess ---
> [INFO] Executing tasks
> [copy] Copying 1 file to /home/jharting/jboss/testing/Weld-1.1.0.Beta1/jboss-6.0.0-SNAPSHOT/server/all/farm
> [echo] Waiting for application at http://localhost:8180/weld-numberguess
> [INFO] Executed tasks
> [INFO]
> [INFO] --- failsafe-maven-plugin:2.4.3-alpha-1:integration-test (integration-test) @ weld-jsf-numberguess ---
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 12.601s
> [INFO] Finished at: Tue Aug 31 12:06:26 CEST 2010
> [INFO] Final Memory: 28M/244M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:failsafe-maven-plugin:2.4.3-alpha-1:integration-test (integration-test) on project weld-jsf-numberguess: Execution integration-test of goal org.codehaus.mojo:failsafe-maven-plugin:2.4.3-alpha-1:integration-test failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:failsafe-maven-plugin:2.4.3-alpha-1:integration-test (integration-test) on project weld-jsf-numberguess: Execution integration-test of goal org.codehaus.mojo:failsafe-maven-plugin:2.4.3-alpha-1:integration-test failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:149)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:124)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution integration-test of goal org.codehaus.mojo:failsafe-maven-plugin:2.4.3-alpha-1:integration-test failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at org.codehaus.mojo.failsafe.IntegrationTestMojo.verifyParameters(IntegrationTestMojo.java:611)
> at org.codehaus.mojo.failsafe.IntegrationTestMojo.execute(IntegrationTestMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
> ... 20 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list