Fixed in r25015. On Fri, Aug 5, 2011 at 4:52 PM, Ralph Castain <r...@open-mpi.org> wrote:
> Thanks Wes - it isn't the print that's the issue, it's the fact that we > have epochs that aren't being initialized, and what else that may be causing > to have problems. > > > On Aug 5, 2011, at 2:45 PM, Wesley Bland wrote: > > I don't think these are anything to worry about since they're all print > statements, but I will work on these tonight. > > On Fri, Aug 5, 2011 at 3:03 PM, Jeff Squyres <jsquy...@cisco.com> wrote: > >> Ralph and I are trying to track down the mysterious ORTE error. >> >> In doing so, I have found at least one fairly repeatable error on my >> cluster: when running through SLURM the ibm/dynamic/spawn test, where we >> mpirun 3 procs and then we MPI_COMM_SPAWN 3 more. Running the orteds >> through valgrind, I see a bunch of uninitialized epoch issues. >> >> Attached at the 2 valgrind outputs. >> >> Can these be fixed? I don't know if they're actual problems or not, but >> seeing uninitialized values go by makes me extremely nervous. >> >> Thanks! >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel >
