Run EI systemtests in Travis build

[e-pettersson-ericsson]

Description

We need to include the system tests in the Travis build. A separate stage should be defined for running the system test to run in parallel with other test stages. The system tests should run on the latest code changes of EI (not using released docker images from Docker hub but instead build the image based on latest code changes).

Benefits

Improved test coverage in Travis.

Possible Drawbacks

None that I can think of.

[e-pettersson-ericsson]

Started looking into this

[e-pettersson-ericsson]

I've set up an environment which can be reused in the integration tests and the system tests, and the environment works good locally but pushing up changes in build to Travis I've got some issues with the availabe resources in the Travis VM. When downloading the maven dependencies to run the system tests the build usually hangs and gives no output for some time (causing the build to abort after a time limit) or gives the error shown below:

An excerpt of the logs:

Downloading from central: http://repo.maven.apache.org/maven2/net/bytebuddy/byte-buddy/1.7.11/byte-buddy-1.7.11.pom
Downloaded from central: http://repo.maven.apache.org/maven2/net/bytebuddy/byte-buddy/1.7.11/byte-buddy-1.7.11.pom (12 kB at 425 kB/s)
Downloading from central: http://repo.maven.apache.org/maven2/net/bytebuddy/byte-buddy-parent/1.7.11/byte-buddy-parent-1.7.11.pom
Downloaded from central: http://repo.maven.apache.org/maven2/net/bytebuddy/byte-buddy-parent/1.7.11/byte-buddy-parent-1.7.11.pom (26 kB at 726 kB/s)
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e1200000, 93323264, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 93323264 bytes for committing reserved memory.
The command "mvn -P systemTest -DsystemtestProperties=src/systemtest/resources/system-test.properties verify " exited with 1.

This happens despite having the system tests in a separate stage in the Travis build.
Not sure how to proceed with this... I've also tried running the 3 system test flows separately, but it doesn't seem to help with this issue...
I'm unassigning myself from this, so if someone else has time to look into this, feel free to do so.

[e-pettersson-ericsson]

I don't see us prioritizing this issue in the near future unfortunately, mostly because we don't have a way around the limitations of the Travis build... Should we close this issue? @eiffel-community/eiffel-intelligence-maintainers ?

[SantoshNC68]

We can add a new label instead of closing the issue, that way someone can also see the issue and try to help us. How about adding "help required" and "blocked" labels ?

[e-pettersson-ericsson]

Ok, I'll add the "help wanted" label for now.