Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
we have problems only when adding new code and need to debug it. will revert back you change. On Tue, Apr 8, 2014 at 1:58 AM, Jeff Squyres (jsquyres) wrote: > On Apr 7, 2014, at 6:39 PM, Mike Dubman wrote: > > > somehow we run it with both, --verbose not enough to understand the > problem and --debug is too much. > > > > maybe --trace is here to rescue? > > It won't really solve the problem; it'll just create another level of > argument about where a given message should go (now there will be 3 levels > instead of 2... eventually there will be 4, and then 5, and then ...). > > Do you really need to run with --debug all the time? I.e., do you have so > many problems with MTT itself that you need to run with --debug? > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel >
Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
On Apr 7, 2014, at 6:39 PM, Mike Dubman wrote: > somehow we run it with both, --verbose not enough to understand the problem > and --debug is too much. > > maybe --trace is here to rescue? It won't really solve the problem; it'll just create another level of argument about where a given message should go (now there will be 3 levels instead of 2... eventually there will be 4, and then 5, and then ...). Do you really need to run with --debug all the time? I.e., do you have so many problems with MTT itself that you need to run with --debug? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
somehow we run it with both, --verbose not enough to understand the problem and --debug is too much. maybe --trace is here to rescue? On Tue, Apr 8, 2014 at 1:36 AM, Jeff Squyres (jsquyres) wrote: > Yes. > > The intent is that --debug is *very* verbose, and is generally only > useful when something goes wrong. > > I run Cisco's automated MTT with only --verbose. > > > > On Apr 7, 2014, at 6:35 PM, Mike Dubman wrote: > > > ohh.. it is just flooding the log with same data for every test launch. > > > > maybe we should have verbose level in mtt? > > > > > > On Mon, Apr 7, 2014 at 6:30 PM, Jeff Squyres (jsquyres) < > jsquy...@cisco.com> wrote: > > Mike -- > > > > Why did you comment these out? By definition, --debug output should be > a LOT of output. > > > > > > On Apr 5, 2014, at 7:27 PM, wrote: > > > > > Author: miked (Mike Dubman) > > > Date: 2014-04-05 19:27:28 EDT (Sat, 05 Apr 2014) > > > New Revision: 1637 > > > URL: https://svn.open-mpi.org/trac/mtt/changeset/1637 > > > > > > Log: > > > silence print > > > > > > Text files modified: > > > trunk/lib/MTT/Values/Functions/MPI/OMPI.pm | 4 ++-- > > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > > > > Modified: trunk/lib/MTT/Values/Functions/MPI/OMPI.pm > > > > == > > > --- trunk/lib/MTT/Values/Functions/MPI/OMPI.pmMon Mar 17 > 14:14:47 2014(r1636) > > > +++ trunk/lib/MTT/Values/Functions/MPI/OMPI.pm2014-04-05 > 19:27:28 EDT (Sat, 05 Apr 2014) (r1637) > > > @@ -331,7 +331,7 @@ > > > > > > # Check the environment for OMPI_MCA_* values > > > foreach my $e (keys(%ENV)) { > > > -Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > > +#Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > > if ($e =~ m/^OMPI_MCA_(\S+)/) { > > > my $v = $ENV{"OMPI_MCA_$1"}; > > > push(@params, "--env-mca $1 $v"); > > > @@ -339,7 +339,7 @@ > > > } > > > > > > $str = join(' ', @params); > > > -Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > > +#Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > > $str; > > > } > > > > > > ___ > > > mtt-svn mailing list > > > mtt-...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn > > > > > > -- > > Jeff Squyres > > jsquy...@cisco.com > > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > ___ > > mtt-devel mailing list > > mtt-de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel > > > > ___ > > mtt-devel mailing list > > mtt-de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel >
Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
Yes. The intent is that --debug is *very* verbose, and is generally only useful when something goes wrong. I run Cisco's automated MTT with only --verbose. On Apr 7, 2014, at 6:35 PM, Mike Dubman wrote: > ohh.. it is just flooding the log with same data for every test launch. > > maybe we should have verbose level in mtt? > > > On Mon, Apr 7, 2014 at 6:30 PM, Jeff Squyres (jsquyres) > wrote: > Mike -- > > Why did you comment these out? By definition, --debug output should be a LOT > of output. > > > On Apr 5, 2014, at 7:27 PM, wrote: > > > Author: miked (Mike Dubman) > > Date: 2014-04-05 19:27:28 EDT (Sat, 05 Apr 2014) > > New Revision: 1637 > > URL: https://svn.open-mpi.org/trac/mtt/changeset/1637 > > > > Log: > > silence print > > > > Text files modified: > > trunk/lib/MTT/Values/Functions/MPI/OMPI.pm | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > > Modified: trunk/lib/MTT/Values/Functions/MPI/OMPI.pm > > == > > --- trunk/lib/MTT/Values/Functions/MPI/OMPI.pmMon Mar 17 14:14:47 > > 2014(r1636) > > +++ trunk/lib/MTT/Values/Functions/MPI/OMPI.pm2014-04-05 19:27:28 > > EDT (Sat, 05 Apr 2014) (r1637) > > @@ -331,7 +331,7 @@ > > > > # Check the environment for OMPI_MCA_* values > > foreach my $e (keys(%ENV)) { > > -Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > +#Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > if ($e =~ m/^OMPI_MCA_(\S+)/) { > > my $v = $ENV{"OMPI_MCA_$1"}; > > push(@params, "--env-mca $1 $v"); > > @@ -339,7 +339,7 @@ > > } > > > > $str = join(' ', @params); > > -Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > +#Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > $str; > > } > > > > ___ > > mtt-svn mailing list > > mtt-...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
ohh.. it is just flooding the log with same data for every test launch. maybe we should have verbose level in mtt? On Mon, Apr 7, 2014 at 6:30 PM, Jeff Squyres (jsquyres) wrote: > Mike -- > > Why did you comment these out? By definition, --debug output should be a > LOT of output. > > > On Apr 5, 2014, at 7:27 PM, wrote: > > > Author: miked (Mike Dubman) > > Date: 2014-04-05 19:27:28 EDT (Sat, 05 Apr 2014) > > New Revision: 1637 > > URL: https://svn.open-mpi.org/trac/mtt/changeset/1637 > > > > Log: > > silence print > > > > Text files modified: > > trunk/lib/MTT/Values/Functions/MPI/OMPI.pm | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > > Modified: trunk/lib/MTT/Values/Functions/MPI/OMPI.pm > > > == > > --- trunk/lib/MTT/Values/Functions/MPI/OMPI.pmMon Mar 17 > 14:14:47 2014(r1636) > > +++ trunk/lib/MTT/Values/Functions/MPI/OMPI.pm2014-04-05 > 19:27:28 EDT (Sat, 05 Apr 2014) (r1637) > > @@ -331,7 +331,7 @@ > > > > # Check the environment for OMPI_MCA_* values > > foreach my $e (keys(%ENV)) { > > -Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > +#Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > > if ($e =~ m/^OMPI_MCA_(\S+)/) { > > my $v = $ENV{"OMPI_MCA_$1"}; > > push(@params, "--env-mca $1 $v"); > > @@ -339,7 +339,7 @@ > > } > > > > $str = join(' ', @params); > > -Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > +#Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > $str; > > } > > > > ___ > > mtt-svn mailing list > > mtt-...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel >
Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI
Mike -- Why did you comment these out? By definition, --debug output should be a LOT of output. On Apr 5, 2014, at 7:27 PM, wrote: > Author: miked (Mike Dubman) > Date: 2014-04-05 19:27:28 EDT (Sat, 05 Apr 2014) > New Revision: 1637 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1637 > > Log: > silence print > > Text files modified: > trunk/lib/MTT/Values/Functions/MPI/OMPI.pm | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > Modified: trunk/lib/MTT/Values/Functions/MPI/OMPI.pm > == > --- trunk/lib/MTT/Values/Functions/MPI/OMPI.pmMon Mar 17 14:14:47 > 2014(r1636) > +++ trunk/lib/MTT/Values/Functions/MPI/OMPI.pm2014-04-05 19:27:28 EDT > (Sat, 05 Apr 2014) (r1637) > @@ -331,7 +331,7 @@ > > # Check the environment for OMPI_MCA_* values > foreach my $e (keys(%ENV)) { > -Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > +#Debug("Functions::MPI::OMPI: Checking env key: $e\n"); > if ($e =~ m/^OMPI_MCA_(\S+)/) { > my $v = $ENV{"OMPI_MCA_$1"}; > push(@params, "--env-mca $1 $v"); > @@ -339,7 +339,7 @@ > } > > $str = join(' ', @params); > -Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > +#Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > $str; > } > > ___ > mtt-svn mailing list > mtt-...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/