... | ... | @@ -43,9 +43,10 @@ Links to main Trilinos CDash dashboard results and query tools: |
|
|
|
|
|
The different categories of Trilinos testing are:
|
|
|
|
|
|
+ [Pull-request testing](Policies--|-Testing#pull_request_testing)
|
|
|
+ [Pull-request Testing](Policies--|-Testing#pull_request_testing)
|
|
|
+ [Deprecated : Pre-push Continuous Integration Testing](Policies--|-Testing#pre_push_ci_testing)
|
|
|
+ [Post-push Continuous Integration Testing](Policies--|-Testing#post_push_ci_testing)
|
|
|
+ [Dev->Master (Develop to Master Branch) Testing](Policies--|-Testing#dev_master_testing)
|
|
|
+ [Nightly Regression Testing](Policies--|-Testing#nightly_regression_testing)
|
|
|
+ [Performance Testing](Policies--|-Testing#performance_testing)
|
|
|
+ [Installation Testing](Policies--|-Testing#installation_testing)
|
... | ... | @@ -60,7 +61,7 @@ These different categories of testing are described in more detail below. |
|
|
|
|
|
**Pull-request testing**: All packages [[Pull Request Builds](https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=3&showfilters=1&filtercombine=and&field1=groupname&compare1=61&value1=Pull%20Request&field2=buildstarttime&compare2=84&value2=now&field3=buildstarttime&compare3=83&value3=4%20weeks%20ago)]
|
|
|
|
|
|
When a new pull request is issued to the trilinos/Trilinos repository [Trilinos/pulls](https://github.com/trilinos/Trilinos/pulls/) this system will create jobs on a set of sandia machines to build and test using gcc 4.8.4 and gcc 4.9.3 and openmpi 1.8.7. Since these builds are not done on the developers machine they are completed and the results are repoted back to the pull request on github as comments. In the future these will include reference to CDASH lines for each build.
|
|
|
When a new pull request is issued to the trilinos/Trilinos repository [Trilinos/pulls](https://github.com/trilinos/Trilinos/pulls/) this system will create jobs on a set of Sandia machines to build and test. The build results for the builds are summarized in the GitHub issue, and are also reported in more detail to CDash in the "Pull Request" group. More detailed information on pull-request testing can be found [here](https://github.com/trilinos/Trilinos/wiki/Pull-Request-Testing-Interface).
|
|
|
|
|
|
<a name="pre_push_ci_testing"/>
|
|
|
|
... | ... | @@ -84,6 +85,14 @@ Emails are sent out by CDash to the different package lists `PACKAGE-regression@ |
|
|
|
|
|
The main purposes for having a post-push CI server running in addition to pre-push CI testing are to: a) quickly catch errors from sloppy (or absent) checkin testing, b) catch violations of the [additive test assumption of branches](https://docs.google.com/document/d/1uVQYI2cmNx09fDkHDA136yqDTqayhxqfvjFiuUue7wo/edit#bookmark=id.d1jneh8ubsyn) which can occur when multiple test/pushes overlap, c) catch problems so they can be fixed before the nightly or weekly tests fire off.
|
|
|
|
|
|
<a name="dev_master_testing"/>
|
|
|
|
|
|
**Dev-Master Testing**: All packages [[Pull Request Builds](https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercombine=and&filtercombine=and&filtercombine=and&filtercombine=and&filtercount=3&showfilters=1&filtercombine=and&field1=groupname&compare1=61&value1=Pull%20Request&field2=buildstarttime&compare2=84&value2=now&field3=buildstarttime&compare3=83&value3=4%20weeks%20ago)]
|
|
|
|
|
|
The purpose of the dev->master branch testing is to provide additional stability checks beyond pull-request testing for users of the master branch.
|
|
|
|
|
|
The dev->master testing process creates a temporary branch from the develop branch, and issues a pull-request against master. The dev->master set of tests is run against that temporary branch and can be merged if all tests pass.
|
|
|
|
|
|
<a name="nightly_regression_testing"/>
|
|
|
|
|
|
**Nightly Regression Testing**: Secondary Tested Code [[Nightly Regression Dashboard](https://testing-vm.sandia.gov/cdash/index.php?project=Trilinos&filtercount=1&showfilters=1&field1=groupname&compare1=61&value1=Nightly)]
|
... | ... | @@ -176,4 +185,4 @@ There is a wealth of information on CDash about the builds that are done, the ve |
|
|
* On the package build summary page `cdash/buildSummary.php?buildid=<pkg-build-id>`, click on the "view notes" link at the top ad the end of the "Build Name" field.
|
|
|
* On the package notes page `cdash/viewNotes.php?buildid=<pkg-build-id>`:
|
|
|
* Click on the "TrilinosRepoVersion.txt" file link to see the top commit from Trilinos being tested
|
|
|
* Click on the "Updates.txt" file link to see the new commits pulled from the last time this build ran |
|
|
* Click on the "Updates.txt" file link to see the new commits pulled from the last time this build ran |
|
|
\ No newline at end of file |