search

TerraME / terrame

TerraME is a programming environment for spatial dynamical modelling
www.terrame.org
GNU Lesser General Public License v3.0
36 stars 13 forks source link

Create jenkins job to run the execution tests #1211

Closed avancinirodrigo closed 8 years ago

avancinirodrigo commented 8 years ago

Analyze what is better way to do this test. The steps to do this test are in: https://github.com/TerraME/terrame/wiki/developing#Testing

I think that this job shouldn't be in pull request's flow because it is big and slow. So, jenkins allow to schedule the jobs.

raphaelrpl commented 8 years ago

The Jenkins execution tests job has been created. It runs every day at 10:49 PM and it is available in http://www.dpi.inpe.br/jenkins/job/terrame-test-execution-linux-ubuntu-14.04/.

pedro-andrade-inpe commented 8 years ago

Is there a way to the remove all the output lines starting with the following lines?

Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension KEYBOARD
raphaelrpl commented 8 years ago

Yes, there is. I have unchecked Log option of GUI Xvfb plugin, so the next test should not display them anymore.

pedro-andrade-inpe commented 8 years ago

Good, the output above was removed. Is there a way to remove the installing output as well?

Install the project...
-- Install configuration: "Release"
-- Installing: /home/jenkins/build-projects/workspace/terrame-repository-test-linux-ubuntu-14.04/912aef2648ce2cc4e96f6d529ac186d3e6407c49/install/bin/terrame
-- Set runtime path of "/home/jenkins/build-projects/workspace/terrame-repository-test-linux-ubuntu-14.04/912aef2648ce2cc4e96f6d529ac186d3e6407c49/install/bin/terrame" to ""
-- Installing: /home/jenkins/build-projects/workspace/terrame-repository-test-linux-ubuntu-14.04/912aef2648ce2cc4e96f6d529ac186d3e6407c49/install/./bin/lua
-- Installing: /home/jenkins/build-projects/workspace/terrame-repository-test-linux-ubuntu-14.04/912aef2648ce2cc4e96f6d529ac186d3e6407c49/install/./bin/lua/utils.lua
-- Installing: /home/jenkins/build-projects/workspace/terrame-repository-test-linux-ubuntu-14.04/912aef2648ce2cc4e96f6d529ac186d3e6407c49/install/./bin/lua/doc.lua
[...]

It represents more than 70% of the whole output and is unnecessary.

raphaelrpl commented 8 years ago

Yeah, there is. I can redirect the make install output to /dev/null. But, the same script of build and installation is used in Linux compilation job in Jenkins. Would you like also to hide it from that job?

pedro-andrade-inpe commented 8 years ago

Yes, but as long as if you guarantee that errors will be shown.

raphaelrpl commented 8 years ago

Sure, i will redirect everything to /dev/null except stderr.

pedro-andrade-inpe commented 8 years ago

Both execution and repository tests are being executed nightly. However, I am getting emails only from repository tests, but not execution tests.

raphaelrpl commented 8 years ago

Oh yes, there is not a Post build action set. I have unmarked for testing schedule to avoid spawn emails. The option has been set again.

pedro-andrade-inpe commented 8 years ago

Just to be clear: the idea is to send emails only if execution tests or repository tests fail. If both fail two emails can be sent. In the next day, if the tests are ok then a confirmation will be sent to say that the problem was fixed. In the next day, if everything is ok then no email will be sent.