I guess this is a problem in the Python interface too, when Exceptions
are raised. If we implement a call to MPIAbort as part of dolfin_error,
it is another argument to not only py3fy all Python exceptions, but to
replace them with calls to dolfin_error.
Johan
On 01/06/2013 05:31 PM, Garth Wells wrote:
> Public bug reported:
>
> DOLFIN can deadlock when one process throws a error and others don't.
> The solution is probably to call MPIAbort when throwing an error.
>
> ** Affects: dolfin
> Importance: High
> Status: New
>
> ** Changed in: dolfin
> Importance: Undecided => High
>
I guess this is a problem in the Python interface too, when Exceptions
are raised. If we implement a call to MPIAbort as part of dolfin_error,
it is another argument to not only py3fy all Python exceptions, but to
replace them with calls to dolfin_error.
Johan
On 01/06/2013 05:31 PM, Garth Wells wrote:
> Public bug reported:
>
> DOLFIN can deadlock when one process throws a error and others don't.
> The solution is probably to call MPIAbort when throwing an error.
>
> ** Affects: dolfin
> Importance: High
> Status: New
>
> ** Changed in: dolfin
> Importance: Undecided => High
>