Abort() must be triggered when an error condition (e.g., an Exception) is locally triggered on a process

[amartinhuertas]

In order to avoid MPI deadlocks we must automatically call MPI.Abort() when an error condition (e.g., a failing test or an exception) is locally triggered on a processor. Problem: how can this be fulfilled when an error condition is produced within an external dependency, such as, e.g., Gridap.jl? Perhaps using Julia built-in support for exceptions? (i.e., try catch statements).

[fverdugo]

Yes, we need some context handling for the MPI library and I think exceptions are the way to go (even though they can be hidden from the user).

My question is if MPI.jl provides some kind of context handling ready to be used? something like

MPI.init() do

# My MPI code here

end

that guarantees that MPI.Finalize or MPI.Abour will be called eventually, even if errors in the do-block are found.

Anyway, we can implement something like:

MPIPETScCommunicator() do comm

# GridapDistributed user code here

end

which internally does exception handling

[amartinhuertas]

solved in 53c0fc7