Takahiro,
I went over this ticket and attached a new patch. Basically I went over all the
possible cases, both in test and wait, and ensure the behavior is always
consistent. Please give it a try, and let us know of the outcome.
Thanks,
George.
On Jan 25, 2013, at 00:53 , "Kawashima, T
Jeff,
I would like to try to get down there (from Menlo Park) to meet and thank the
OpenMPI developers, but I doubt I would be a very useful participant. Will
there be a social event that I could attend? Maybe there is one at the MPI
Forum? Because of the US budget sequestration, I cannot sp
We are having a developer's meeting right before the MPI Forum meeting in June,
2013. All are welcome to attend. Two primary topics for this meeting will be:
a) progress since the UTK meeting on moving the BTLs down to OPAL, and b)
asynchronous progress.
*** PLEASE SIGN UP ON THE WIKI PAGE SO
On Apr 30, 2013, at 9:41 AM, George Bosilca wrote:
> Ralph,
>
> The log message is plain wrong. There is nothing non standard compliant in
> the way the PML V is using the output, it is just it use an internal storage
> for it's stream.
My point was that vprotocol isn't a standalone framewor
Ralph,
The log message is plain wrong. There is nothing non standard compliant in the
way the PML V is using the output, it is just it use an internal storage for
it's stream.
It should be straightforward to fix it by removing __ALL__ references to the
output variable not only the one from the
This commit broke the trunk.
George.
On Apr 30, 2013, at 17:21 , svn-commit-mai...@open-mpi.org wrote:
> Author: hjelmn (Nathan Hjelm)
> Date: 2013-04-30 11:21:42 EDT (Tue, 30 Apr 2013)
> New Revision: 28417
> URL: https://svn.open-mpi.org/trac/ompi/changeset/28417
>
> Log:
> vprotocol: remov
...I see Nathan raising his hand...
:-)
Is there a way we can get opal_output / OPAL_OUTPUT to give us some help when
this happens? E.g., output a warning that it's been given an invalid stream
ID? I know we declare -1 as a valid output (effectively to the bitbucket); is
there a unique way t