Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

2014-04-07 Thread Jeff Squyres (jsquyres)
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:

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

2014-04-07 Thread Mike Dubman
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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

2014-04-07 Thread Jeff Squyres (jsquyres)
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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

2014-04-07 Thread Mike Dubman
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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

2014-04-07 Thread Jeff Squyres (jsquyres)
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