Hearing no dissent, I’ll go ahead and send the new text to the mailing list. We’ll discuss the changes on the call tomorrow in case there are any objections.
Thanks,
Wesley
> On May 23, 2016, at 8:19 AM, Bland, Wesley <wesley.bland(a)intel.com> wrote:
>
> Hi working group,
>
> I realized this morning that we never tackled one of pieces of feedback we got at the last reading for catastrophic error codes. The forum wanted us to add a new API function that would indicate whether the MPI library has ever returned a catastrophic error code. I put something together quickly this morning and I’d appreciate people taking a look at it so I can send it out to the full forum before the deadline today.
>
> The diff with the addition can be found here:
>
> https://github.com/mpiwg-ft/mpi-standard/commit/7826a75a14f12ad8f4a399225d5…
>
> Please make any comments on that diff page or via email quickly so I can iterate before this afternoon.
>
> Thanks,
> Wesley
>
Hi working group,
I realized this morning that we never tackled one of pieces of feedback we got at the last reading for catastrophic error codes. The forum wanted us to add a new API function that would indicate whether the MPI library has ever returned a catastrophic error code. I put something together quickly this morning and I’d appreciate people taking a look at it so I can send it out to the full forum before the deadline today.
The diff with the addition can be found here:
https://github.com/mpiwg-ft/mpi-standard/commit/7826a75a14f12ad8f4a399225d5…
Please make any comments on that diff page or via email quickly so I can iterate before this afternoon.
Thanks,
Wesley
