Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLOSED: Improve TrilinosInstallTests to make more clear (#10896) #10911

Conversation

bartlettroscoe
Copy link
Member

Duplicate of #10897 but with an even-numbered PR ID so it will get run by the PR tester (see #10858 (comment)) :-)

Based on the confusion by a Trilinos developer that creatd issue trilinos#10896, I
have improved these installation tests in the following way:

* Made it clear that the doInstall test will fail if there are **any** build
  errors in the project

* Print out the install errors to make it clear why the install failed

* Use CTest test fixtures to skip the find_package(Trilinos) and
  simpleBuildAgainstTrilinos tests if the doInstall test fails
@bartlettroscoe bartlettroscoe added the PA: Framework Issues that fall under the Trilinos Framework Product Area label Aug 21, 2022
@bartlettroscoe
Copy link
Member Author

Shoot, this turned out to be an odd-numbered PR so it will not get tested. Closing and will open a new PR.

@bartlettroscoe bartlettroscoe changed the title Improve TrilinosInstallTests to make more clear (#10896) CLOSED: Improve TrilinosInstallTests to make more clear (#10896) Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PA: Framework Issues that fall under the Trilinos Framework Product Area
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant