Serge Huber created UNOMI-72:
--------------------------------

             Summary: Fix integration and performance tests
                 Key: UNOMI-72
                 URL: https://issues.apache.org/jira/browse/UNOMI-72
             Project: Apache Unomi
          Issue Type: Bug
          Components: core
    Affects Versions: 1.2.0-incubating
            Reporter: Serge Huber
             Fix For: 1.2.0-incubating


Since we moved to ElasticSearch 5.x and externalized the ES server, the 
integration and performance tests are broken. We should fix them but this is 
not easy since we need to somehow startup an ES server.

We tried using the following pom.xml plugin configuration : 

{code}
            <plugin>
                <groupId>com.github.alexcojocaru</groupId>
                <artifactId>elasticsearch-maven-plugin</artifactId>
                <!-- REPLACE THE FOLLOWING WITH THE PLUGIN VERSION YOU NEED -->
                <version>5.0</version>
                <configuration>
                    <clusterName>contextElasticSearch</clusterName>
                    <transportPort>9300</transportPort>
                    <httpPort>9200</httpPort>
                    <version>5.0.2</version>
                </configuration>
                <executions>
                    <!--
                        The elasticsearch maven plugin goals are by default 
bound to the
                        pre-integration-test and post-integration-test phases
                    -->
                    <execution>
                        <id>start-elasticsearch</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>runforked</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>stop-elasticsearch</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>stop</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-failsafe-plugin</artifactId>
                <configuration>
                    <includes>
                        <include>**/*AllITs.java</include>
                    </includes>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>integration-test</goal>
                            <goal>verify</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
{code}

but it fails with the following errors : 

{code}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:08 min
[INFO] Finished at: 2017-01-10T20:55:49+01:00
[INFO] Final Memory: 96M/919M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test 
(default) on project unomi-itests: Execution default of goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test failed: 
The forked VM terminated without properly saying goodbye. VM crash or 
System.exit called?
[ERROR] Command was /bin/sh -c cd 
/Users/loom/java/technologies/apache-git/incubator-unomi/itests && 
/Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/jre/bin/java 
-jar 
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefirebooter410416926696253620.jar
 
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire3550479375448672288tmp
 
/Users/loom/java/technologies/apache-git/incubator-unomi/itests/target/surefire/surefire_0105027550392275185tmp
[ERROR] -> [Help 1]
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to