forked from trilinos/Trilinos
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'develop' of https://github.com/searhein/Trilinos into p…
…artition-of-unity * 'develop' of https://github.com/searhein/Trilinos: (100 commits) Change initializer list order to make g++ happy Plumbing for BelosBlockCGSolMgr so that Assert Positive Definiteness flag gets passed to BelosCGIter Change Spack module from SuperLUDist 6.2.0 to 5.4.0 (CDOFA-66) Testing: Tpetra: make nightly build faster Update CrsMatrix_UnitTests4.cpp Tpetra: Fixes so that trilinos#6076 can pass MueLu: rebasing the gold files for phase 3 refactored outputs MueLu: refactor of Phase3 aggregation, see issue trilinos#5838 KokkosKernels - trsm transpose does not solve the problem correctly. Belos: treats cases where numResTests is zero Belos: removes a int cast warning and removes one unnecessary StatusTestCombo cast Belos: removes a int cast warning and removes one unnecessary StatusTestCombo cast Reduced from ctest -j8 to -j4 for all CUDA builds (trilinos#6052) Belos: solves Issue trilinos#6059 Belos: solves Issue trilinos#6059 ML: Code cleanup to RefMaxwell ML: Removing supperfluous import constructor ML: Adding new support routine Xpetra: disable Map cloner test if no Tpetra deprecated Phalanx - wrong number of kokkos allocation arguments. ...
- Loading branch information
Showing
537 changed files
with
10,276 additions
and
3,972 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,77 +1,63 @@ | ||
<!--- | ||
Be sure to select `develop` as the `base` branch against which to create this | ||
pull request. Only pull requests against `develop` will undergo Trilinos' | ||
automated testing. Pull requests against `master` will be ignored. | ||
Provide a general summary of your changes in the Title above. If this pull | ||
request pertains to a particular package in Trilinos, it's worthwhile to start | ||
the title with "PackageName: ". | ||
Note that anything between these delimiters is a comment that will not appear | ||
in the pull request description once created. Most areas in this message are | ||
commented out and can be easily added by removing the comment delimiters. | ||
Please make sure to mark: | ||
* Reviewers | ||
* Assignees | ||
* Labels | ||
Replace <teamName> below with the appropriate Trilinos package/team name. | ||
--> | ||
@trilinos/<teamName> | ||
|
||
## Description | ||
<!--- Please describe your changes in detail. --> | ||
|
||
## Motivation and Context | ||
<!--- Why is this change required? What problem does it solve? --> | ||
|
||
<!--- | ||
If applicable, let us know how this merge request is related to any other open | ||
issues or pull requests: | ||
## Related Issues | ||
* Closes | ||
* Blocks | ||
* Is blocked by | ||
* Follows | ||
* Precedes | ||
* Related to | ||
* Part of | ||
* Composed of | ||
--> | ||
|
||
## How Has This Been Tested? | ||
<!--- | ||
Please describe in detail how you tested your changes. Include details of your | ||
testing environment and the tests you ran to see how your change affects other | ||
areas of the code. Consider including configure, build, and test log files. | ||
--> | ||
|
||
<!--- | ||
## Screenshots | ||
Not obligatory, but is there anything pertinent that we should see? | ||
--> | ||
|
||
<!--- | ||
Go over all the following points, and put an `x` in all the boxes that apply. | ||
If you are unsure about any of these, please ask—we are here to help. | ||
--> | ||
|
||
## Checklist | ||
|
||
- [ ] My commit messages mention the appropriate GitHub issue numbers. | ||
- [ ] My code follows the code style of the affected package(s). | ||
- [ ] My change requires a change to the documentation. | ||
- [ ] I have updated the documentation accordingly. | ||
- [ ] I have read the [code contribution guidelines](../blob/master/CONTRIBUTING.md) for this project. | ||
- [ ] I have added tests to cover my changes. | ||
- [ ] All new and existing tests passed. | ||
- [ ] No new compiler warnings were introduced. | ||
- [ ] These changes break backwards compatibility. | ||
|
||
<!--- | ||
## Additional Information | ||
Anything else we need to know in evaluating this merge request? | ||
--> | ||
<!--- | ||
Be sure to select `develop` as the `base` branch against which to create this | ||
pull request. Only pull requests against `develop` will undergo Trilinos' | ||
automated testing. Pull requests against `master` will be ignored. | ||
Provide a general summary of your changes in the Title above. If this pull | ||
request pertains to a particular package in Trilinos, it's worthwhile to start | ||
the title with "PackageName: ". | ||
Note that anything between these delimiters is a comment that will not appear | ||
in the pull request description once created. Most areas in this message are | ||
commented out and can be easily added by removing the comment delimiters. | ||
Please make sure to mark: | ||
* Reviewers | ||
* Assignees | ||
* Labels | ||
Replace <teamName> below with the appropriate Trilinos package/team name. | ||
--> | ||
@trilinos/<teamName> | ||
|
||
## Motivation | ||
<!--- | ||
Why is this change required? What problem does it solve? Please link to a github | ||
issue that describes the problem/issue/bug this PR solves. | ||
--> | ||
|
||
<!--- | ||
If applicable, let us know how this merge request is related to any other open | ||
issues or pull requests: | ||
## Related Issues | ||
* Closes | ||
* Blocks | ||
* Is blocked by | ||
* Follows | ||
* Precedes | ||
* Related to | ||
* Part of | ||
* Composed of | ||
--> | ||
|
||
|
||
## Stakeholder Feedback | ||
<!--- | ||
If a github issue includes feedback from the relevant stakeholder(s), please link it. | ||
If the stakeholder(s) communicated that feedback through a different medium, please note that you did so. | ||
--> | ||
|
||
## Testing | ||
<!--- | ||
Please confirm that any classes or functions in the Trilinos library that this PR touches are | ||
exercised by at least one test in Trilinos. Please specify which test that is. For untestable | ||
changes (e.g. changes to the nightly testing system) or changes to Trilinos tests, please say "N/A". | ||
--> | ||
|
||
<!--- | ||
## Additional Information | ||
Anything else we need to know in evaluating this merge request? | ||
--> |
5 changes: 0 additions & 5 deletions
5
...m/sems-rhel7/drivers/Trilinos-atdm-sems-rhel7-intel-17.0.1-openmp-complex-shared-debug.sh
This file was deleted.
Oops, something went wrong.
5 changes: 0 additions & 5 deletions
5
...hel7/drivers/Trilinos-atdm-sems-rhel7-intel-17.0.1-openmp-complex-shared-release-debug.sh
This file was deleted.
Oops, something went wrong.
File renamed without changes.
File renamed without changes.
5 changes: 0 additions & 5 deletions
5
...vers/atdm/sems-rhel7/drivers/Trilinos-atdm-sems-rhel7-intel-18.0.5-openmp-static-debug.sh
This file was deleted.
Oops, something went wrong.
5 changes: 0 additions & 5 deletions
5
...m/sems-rhel7/drivers/Trilinos-atdm-sems-rhel7-intel-18.0.5-openmp-static-release-debug.sh
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.