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.
For the visualization it would be really nice to see how well tested a
particular interconnect, resource manager, and/or 'feature' is when
ramping up to a release. However these peices of information are hard
to obtain, and in some cases quantify (e.g., what do we mean by
testing a 'feature'?).
Thinking about this it occurred to me that what we really need is for
OMPI to tell MTT what it is doing for some of these cases.
Two examples, MTT cannot tell:
- which set of compile time options are enabled/disabled automatically
e.g. [ "./configure --with-foo" vs "./configure"]
- which BTL(s) or MTL are used to run a test
e.g. [ "mpirun -mca btl tcp,self foo" vs. "mpirun foo"]
For the configure options we *could* parse the config.log to extract
this data. The question is, if we did this, what do we want to look?
And is this something we want to do? Is there another way?
For the BTL(s)/MTL this is a much more subtle question since this
depends on the connectivity of the interfaces on a machine, and the
runtime selection logic. If we added a parameter to mpirun (e.g. "--
showme connectivity") that displayed connectivity information to
stdout (or a file) would this be useful? What should it look like?
We have talked about some of this in the past, but I could not find a
Bug talking about it in MTT.
What do you think about this?