July 2008 - Mpich2-core - mailman3.cels.anl.gov

Migrating to TRAC
by Pavan Balaji 03 Aug '08

03 Aug '08

FYI, Rick and I are working on moving mpich2-maint to use TRAC. The move should be instantaneous as soon as we figure out how to do it :-). Hope nothing gets messed up. Or else we can just start with a clean slate :-). (Sent from my iPhone) -- Pavan Balaji http://www.mcs.anl.gov

6 10

Question about tests
by William Gropp 02 Aug '08

02 Aug '08

The old new testing system that I had started included some tests between different machines to ensure that node-to-node worked. The normal tests usually run on a single machine. Are we regularly running any cross-node tests, and if so, where are they? The tests were those that the wiki page calls "Results from the MPICH2 test suite". (My concern is that Nemesis is detecting that it can used shared memory and we're not testing TCP; alternately, we're always testing TCP and never shared memory). Bill William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

6 16

[Fwd: Cron <buntinas@schwinn> /home/MPI/nightly/basictests -arch=IA32-Linux-GNU]
by Darius Buntinas 02 Aug '08

02 Aug '08

Before I go digging into this myself, does anyone know where this is coming from? -d -------- Original Message -------- Subject: Cron <buntinas@schwinn> /home/MPI/nightly/basictests -arch=IA32-Linux-GNU Date: Wed, 30 Jul 2008 05:28:19 -0500 (CDT) From: root(a)mcs.anl.gov (Cron Daemon) To: buntinas(a)mcs.anl.gov checkbuilds: Unrecognized argument --enable-nemesis-dbg-localoddeven checkbuilds: Unrecognized argument --enable-nemesis-dbg-localoddeven

3 5

Re: [Systems Req #51537] FW: [mpich2-maint] Spam mail
by Rick Bradshaw 31 Jul '08

31 Jul '08

I believe I have stopped the bouncing, for now. We are going to have to architect a better system by which to filter out spam before it hits the trac server though, as this will continue to happen. Rick Rajeev Thakur wrote: > We are getting too many of these mails in response to a spam mail sent to > mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks > like they are just bouncing back and forth. > > Rajeev > > -----Original Message----- > From: owner-mpich2-bugs(a)mcs.anl.gov [mailto:[email protected]] > On Behalf Of mpich2 > Sent: Thursday, July 31, 2008 10:03 AM > To: undisclosed-recipients: > Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server > BNSTORNOTES-M03/Servers/ScotiabankGroup from server > BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the > Domino Directory. > > ---------------------------------------+-------------------------------- > ---------------------------------------+---- > Reporter: Postmaster(a)scotiabank.com | Type: bug > Status: new | Priority: major > Component: mpich2 | > ---------------------------------------+-------------------------------- > ---------------------------------------+---- > > > Your message > > Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server > BNSTORNOTES-M03/Servers/ScotiabankGroup from server > BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the > Domino Directory. > > was not delivered to: > > mailhelp(a)scotiabank.com > > because: > > No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from > server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents > in the Domino Directory. > > > > Notice of Confidentiality: > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review re-transmission dissemination or other use of or > taking of any action in reliance upon this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error please contact the sender immediately by return electronic > transmission and then immediately delete this transmission including all > attachments without copying distributing or disclosing same. > > Avis de confidentialitï¿½: > Lï¿½information transmise est strictement rï¿½servï¿½e ï¿½ la personne ou ï¿½ > lï¿½organisme auquel elle est adressï¿½e et peut ï¿½tre de nature confidentielle. > Toute lecture retransmission divulgation ou autre utilisation de cette > information ou toute action prise sur la foi de cette information par des > personnes ou organismes autres que son destinataire est interdite. Si vous > avez reï¿½u cette information par erreur veuillez contacter son expï¿½diteur > immï¿½diatement par retour du courrier ï¿½lectronique puis supprimer cette > information y compris toutes piï¿½ces jointes sans en avoir copiï¿½ divulguï¿½ ou > diffusï¿½ le contenu. > > Aviso de Confidencialidad. > Este correo electrï¿½nico y/o el material adjunto es para uso exclusivo de > la persona o entidad a la que expresamente se le ha enviado y puede > contener informaciï¿½n confidencial o material privilegiado. Si usted no es > el destinatario legï¿½timo del mismo por favor repï¿½rtelo inmediatamente al > remitente del correo y bï¿½rrelo. Cualquier revisiï¿½n retransmisiï¿½n difusiï¿½n > o cualquier otro uso de este correo por personas o entidades distintas a > las del destinatario legï¿½timo queda expresamente prohibido. Este correo > electrï¿½nico no pretende ni debe ser considerado como constitutivo de > ninguna relaciï¿½n legal contractual o de otra ï¿½ndole similar. > > > -- > Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12> > > >

4 5

FW: [mpich2-maint] Spam mail
by Rajeev Thakur 31 Jul '08

31 Jul '08

We are getting too many of these mails in response to a spam mail sent to mpich2-maint, which is now run by Trac. Is there a way to stop them? Looks like they are just bouncing back and forth. Rajeev -----Original Message----- From: owner-mpich2-bugs(a)mcs.anl.gov [mailto:[email protected]] On Behalf Of mpich2 Sent: Thursday, July 31, 2008 10:03 AM To: undisclosed-recipients: Subject: [mpich2-maint] #12: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory. ---------------------------------------+-------------------------------- ---------------------------------------+---- Reporter: Postmaster(a)scotiabank.com | Type: bug Status: new | Priority: major Component: mpich2 | ---------------------------------------+-------------------------------- ---------------------------------------+---- Your message Subject: [mpich2-maint] #11: DELIVERY FAILURE: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUBM02/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory. was not delivered to: mailhelp(a)scotiabank.com because: No route found to server BNSTORNOTES-M03/Servers/ScotiabankGroup from server BNSHUB01/H/SCOTIABANKGROUP. Check Server and Connection documents in the Domino Directory. Notice of Confidentiality: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review re-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error please contact the sender immediately by return electronic transmission and then immediately delete this transmission including all attachments without copying distributing or disclosing same. Avis de confidentialitï¿½: Lï¿½information transmise est strictement rï¿½servï¿½e ï¿½ la personne ou ï¿½ lï¿½organisme auquel elle est adressï¿½e et peut ï¿½tre de nature confidentielle. Toute lecture retransmission divulgation ou autre utilisation de cette information ou toute action prise sur la foi de cette information par des personnes ou organismes autres que son destinataire est interdite. Si vous avez reï¿½u cette information par erreur veuillez contacter son expï¿½diteur immï¿½diatement par retour du courrier ï¿½lectronique puis supprimer cette information y compris toutes piï¿½ces jointes sans en avoir copiï¿½ divulguï¿½ ou diffusï¿½ le contenu. Aviso de Confidencialidad. Este correo electrï¿½nico y/o el material adjunto es para uso exclusivo de la persona o entidad a la que expresamente se le ha enviado y puede contener informaciï¿½n confidencial o material privilegiado. Si usted no es el destinatario legï¿½timo del mismo por favor repï¿½rtelo inmediatamente al remitente del correo y bï¿½rrelo. Cualquier revisiï¿½n retransmisiï¿½n difusiï¿½n o cualquier otro uso de este correo por personas o entidades distintas a las del destinatario legï¿½timo queda expresamente prohibido. Este correo electrï¿½nico no pretende ni debe ser considerado como constitutivo de ninguna relaciï¿½n legal contractual o de otra ï¿½ndole similar. -- Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/12>

1 0

MPICH2 BoF?
by Rajeev Thakur 30 Jul '08

30 Jul '08

The SC BoF deadline is coming up: July 31st. We are wondering if we should have an MPICH2 BoF again this year. We had one last year for the first time. It was ok I think -- not great, but not bad either. The main difficulty was in getting enough questions from the audience. The main reason to have a BoF is because Open MPI has one. Another option is to have a more focussed one on something like PMI2, although it is hard to get any detailed technical discussion going in a BoF. Any suggestions? Rajeev

6 14

Re: Release housekeeping
by William Gropp 25 Jul '08

25 Jul '08

(I'm resending this because ANL rejected my original reply) Yes, I'm looking at those pages (I'm getting to them through http:// wiki.mcs.anl.gov/mpich2/index.php/Developer_Documentation ). The global symbols one has a date of yesterday, and the "ch3" results are clearly for nemesis (the socksm.o file is in the newtcp netmod). The style checker output is recent as well (no dcmfd items). Special tests must be run manually. The reason that I know about the memory leaks is that I *always* run with --enable-g=log,mem,dbg --enable-posix=strict This gives me the earliest warning that there may be problems and great flexibility (because of enable-g=log,dbg) in getting more info about any problems (which is also why the various printfs should use the dbg or log macros - that way, there is a common and available way to enable them when you need them). Bill William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

4 8

duplicate functions
by Darius Buntinas 25 Jul '08

25 Jul '08

I noticed some duplicate functions in the datatype creation code. E.g., there's a DLOOP_Type_blockindexed_count_contig() function in .../datatype/dataloop/dataloop_create_blockindexed.c and a MPIDI_Type_blockindexed_count_contig() function in .../datatype/mpid_type_blockindexed.c. These look to be identical after macro expansion. Is there a reason that I shouldn't remove one? My plan is to make the functions like DLOOP_Type_blockindexed_count_contig into PREPEND_PREFIX(DLOOP_Type_blockindexed_count_contig) and remove the MPID_ versions. Does this make sense? -d

2 2

Debug util defn/decls in mpiimpl
by Jayesh Krishna 25 Jul '08

25 Jul '08

Hi, I see defns/decls related to debug utils, MPIU_dbg* (the generic ones), in mpiimpl.h. Shouldn't they be in mpidbg.h ? Regards, Jayesh

1 0

Intel tests failures
by William Gropp 25 Jul '08

25 Jul '08

Now that MPI 2.1 allows graph edges to self, I've removed the Intel test that requires an error detection in that case. Bill William Gropp Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign

2 2