Improved traceback from PETSc errors #4616
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There is no need to maintain obsolete
CHKERR
andSETERR
implementations in Firedrake.PETSc management of tracebacks from Cython/Python was improved one year ago in https://gitlab.com/petsc/petsc/-/merge_requests/7938, and now we can get valuable information from catching errors.
Needs
CHKERRMPI
exposed in https://gitlab.com/petsc/petsc/-/merge_requests/8758For example, adding mixing INSERT and ADD values will trigger an error in the PETSc C code that will be forwarded appropriately (through
PETSC_ERR_PYTHON
) to the Python runtime (the patch is for the code in this PR)With the current firedrake code, we get
while with the code in this PR