This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
WHAT: Merge the OPAL SOS development branch into the OMPI trunk.
WHY: Bring over some of the work done to enhance error reporting
WHERE: opal/util/ and a few changes in the ORTE notifier.
TIMEOUT: April 6, Wednesday, COB.
REFERENCE BRANCHES: http://bitbucket.org/jsquyres/opal-sos-fixed/
The OPAL SOS framework tries to meet the following objectives:
- Reduce the cascading error messages and the amount of code needed to
print an error message.
- Build and aggregate stacks of encountered errors and associate
related individual errors with each other.
- Allow registration of custom callbacks to intercept error events.
The SOS system provides an interface to log events of varying
severities. These events are associated with an "encoded" error code
which can be used to refer to stacks of SOS events. When logging
events, they can also be transparently relayed to all the activated
The SOS system is described in detail on this wiki page:
Feel free to comment and/or provide suggestions.