PRJenkins

Testing pull request with Jenkins

Every Pull Request submitted to the ompi or ompi-release repositories is monitored by Mellanox Jenkins server which will start smoke-testing for it.

• The test script repository is here: https://github.com/mellanox-hpc/jenkins_scripts

• The test script for OMPI is here: https://github.com/mellanox-hpc/jenkins_scripts/blob/master/ompi/ompi_jenkins.sh

The smoke-testing contains packs of tests:

• build - run autogen/configure/make sequence (default: on)
• examples - build and run examples from ompi source tree (default: on)
• threads - build ompi with threads support and run thread tests (default: on)
• src_rpm - create ompi.src.rpm (default: on) - (run make distclean, make distcheck, create src.rpm)
• check - runs "make check" after build (default: on)
• help_txt - runs contrib/check-help-strings.pl and test help files (default: off)
• oshmem - runs oshmem tests (default: on)
• vader - runs vader tests (default: on)
• known_issues - run tests for known issues (default: off)
• cov - run coverity tests and generate html report (default: on)
• all - do all of the above (default: off)

In order to select specific test packs for submitted pull request - one should update PR title (check "Edit" button next to the title) with a string in the following format:

jenkins: check,help_txt,threads,src_rpm

and add comment to the PR, in form:

bot:retest

Also, it is possible to unselect specific test kits and re-run jenkins on PR. To unselect specific tests - please add "no" to the test token name, i.e.

jenkins: nosrc_rpm,nocheck
bot: retest

Viewing Jenkins tests result online

• The Jenkins test results for Pull requests for v1.8 branch can be found here:

http://bgate.mellanox.com/jenkins/job/gh-mellanox-v1.8-PR/

• The Jenkins test results for Pull requests for master branch can be found here:

http://bgate.mellanox.com/jenkins/job/gh-ompi-master-pr/

• The jenkins test results for Merge commits to the master branch can be found here:

http://bgate.mellanox.com/jenkins/job/gh-ompi-master-merge/

• When viewing results online, you can browse for every job: ** coverity report ** check job console for error details ** access job workspace and extract files from the build area (src.rpm, tarball, config.log,...)

How to restart Jenkins testing

Every newly submitted PR will be tested by Jenkins automatically, based on PR title jenkins directives (if no present - default tests packs will be used).

Jenkins will retest PR if it was updated with new code or new comment added with a string:

bot:retest

Happy testing!