Ralph,
One more thing. Even with XML enabled, I notice that some error
messages are still sent to stderr without XML tags (see below.) Any
chance these could be sent to stdout wrapped in tags?
Thanks,
Greg
$ mpirun -mca orte_show_resolved_nodenames 1 -xml -display-map -np 1 ./
pop pop_in
Hi Greg
I can catch most of these and will do so as they flow through a single
code path. However, there are places sprinkled throughout the code
where people directly output warning and error info - these will be
more problematic and represent a degree of change that is probably
outside
Hi Ralph,
Cool!
Regarding the scope of the tags, I never really thought about output
from the command itself. I propose that any output that can't
otherwise be classified be sent using the appropriate or
tags with no "rank" attribute.
Cheers,
Greg
On Aug 20, 2009, at 1:52 PM, Ralph Ca
Okay - try r21858.
Ralph
On Aug 20, 2009, at 12:36 PM, Greg Watson wrote:
Hi Ralph,
Cool!
Regarding the scope of the tags, I never really thought about output
from the command itself. I propose that any output that can't
otherwise be classified be sent using the appropriate or
tags w
Ralph,
I'm a little bit concerned about the commits stated below as their
quality doesn't match the usual quality standards of the trunk. There
are several issues: mostly empty files, names coming from other
frameworks, failure to compile on several platforms (including Linux
and MAC OS X
Hmmm...I'm afraid I cannot entirely substantiate your concerns.
Everything compiles just fine for me under both Linux and OSX. True,
the files are not completely instantiated on the trunk at this time,
but they also are not activated on the trunk for precisely that reason.
Can you provide a
