Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Adding more information that may be related. We get OutOfMemoryErrors using
this plugin with any significant number of tests. We even went so far as to
explicitly change the rf version the plugin uses from the default 2.6.3 to the
newest 2.7.3. Since we didn't see this issue before using the plugin (we were
using the main method of org.robotframework.RobotFramework) it appears this
issue is in the plugin.
A stack trace below, heap space issues (probably causing the symptom of GC
Limit Exceeded listed above). Also, there is not a helpful stack trace above
(looks truncated) as the issue appears to be in the plugin, not python.
[INFO] Final Memory: 87M/247M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.googlecode.robotframework-maven-plugin:robotf
ramework-maven-plugin:1.1.2:run (default) on project edw-parsers-csv: Failed to
execute RobotFramework test cases. Check the logs for details. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal c
om.googlecode.robotframework-maven-plugin:robotframework-maven-plugin:1.1.2:run
(default) on project edw-parsers-csv: Failed to execute RobotFramework test case
s. Check the logs for details.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute Rob
otFramework test cases. Check the logs for details.
at com.googlecode.RobotFrameworkMojo.subclassExecute(RobotFrameworkMojo.
java:67)
at com.googlecode.AbstractMojoWithLoadedClasspath.execute(AbstractMojoWi
thLoadedClasspath.java:46)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
... 19 more
[ERROR]
[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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
Original comment by paul.mer...@beaufortfairmont.com
on 28 Sep 2012 at 2:52
This issue may be due to "splitOutputs", which is not supported in the newer
version
Original comment by seanogoc...@gmail.com
on 10 Oct 2012 at 1:56
Original issue reported on code.google.com by
seanogoc...@gmail.com
on 20 Jun 2012 at 1:20