Repository navigation
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 7 |
| Duplication | 0 |
🟢 Coverage 100.00% diff coverage · +0.05% coverage variation
Metric Results Coverage variation ✅ +0.05% coverage variation Diff coverage ✅ 100.00% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (f2da0cd) 51844 33084 63.81% Head commit (5943240) 103746 (+51902) 66252 (+33168) 63.86% (+0.05%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#624) 30 30 100.00% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Terminate all MPI processes when one of them raises an uncaught exception in
psydac.utilities.parallel_utils.parallel_run_from_cli(fixes #621).Without this, the other processes hang as soon as they wait for a message from the failing one, and a job on a cluster keeps its allocation until it reaches the wall-time limit. The same mechanism as in the launcher
python -m mpi4pyis used: the exception is passed tompi4py.run.set_abort_statusand re-raised, hence its traceback is printed and the failing process is cleaned up, thenMPI_Abortis called at exit. This works with any MPI launcher (e.g.mpirun,mpiexec, orsrunin a batch job), and does not require running scripts withpython -m mpi4py.parallel_run_from_cli, abort all processes at exit in case of an uncaught exception inmain, and document this behavior in the docstringdocs/source/examples.rst), which very strongly recommends running every parallel script throughparallel_run_from_clipsydac.utilities.tests.test_parallel_utils, which testsparallel_run_from_cliin serial with and without an exception inmain(the call toMPI_Abortis mocked)The abort was also checked manually with a script failing on one of 4 processes: with the fix, the job terminates with exit code 1 after printing the traceback; without it, the job hangs.