-
Notifications
You must be signed in to change notification settings - Fork 572
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
Belos: Add method to clear custom solver factories #12406
Conversation
Custom solver factories can be provided to the default solver factory that contains classic Belos solvers. Once a custom solver factory is added, it is available to all other solver factories. However, this requires that any custom solver factories are cleared from the default solver factory to avoid memory leaks. This issue resulted in the failure of the custom solver factory test under a debug build. A new method has been added to the solver factory base class to clear any custom solver factories that have been registered with it. The new method is used in the custom solver factory test, enabling clean execution under a debug build.
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-11.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_intel-2021.3
Jenkins Parameters
Using Repos:
Pull Request Author: hkthorn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look reasonable, thanks for chasing this down and the fix!
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: Trilinos_PR_gcc-8.3.0
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-serial
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_gcc-8.3.0-debug
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_clang-11.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_python3
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_cuda-11.4.2-uvm-off
Jenkins Parameters
Build InformationTest Name: Trilinos_PR_intel-2021.3
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ ndellingwood ]! |
Status Flag 'Pull Request AutoTester' - Pull Request will be Automerged |
Merge on Pull Request# 12406: IS A SUCCESS - Pull Request successfully merged |
@trilinos/belos
Motivation
Custom solver factories can be provided to the default solver factory
that contains classic Belos solvers. Once a custom solver factory is
added, it is available to all other solver factories. However, this
requires that any custom solver factories are cleared from the default
solver factory to avoid memory leaks. This issue resulted in the
failure of the custom solver factory test under a debug build, as shown
in issue #11137.
A new method has been added to the solver factory base class to clear
any custom solver factories that have been registered with it. The
new method is used in the custom solver factory test, enabling clean
execution under a debug build.
Stakeholder Feedback
Testing
OSX Clang Serial / MPI