Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all MTT Users mailing list

From: Ethan Mallove (ethan.mallove_at_[hidden])
Date: 2007-01-19 11:21:11


On Fri, Jan/19/2007 08:55:26AM, Tim Mattox wrote:
> Hi All,
>
> On 1/18/07, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> > On Jan 18, 2007, at 10:37 PM, Tim Mattox wrote:
> [snip description of a newline bug]
>
> > Fixed -- none have newlines now, so they'll all be in the one-line
> > output format.
>
> Thanks.
>
> > > I don't know if it is related or not, but for tests that fail without
> > > timing out,
> > > the debug output from MTT for that test does NOT have a line like
> > > these:
> > > test_result: 1 (passed)
> > > test_result: 2 (skipped)
> > > test_result: 3 (timed out)
> >
> > Are you sure? Lines 80-84 of Correctness.pm are:
> >
> > if ($results->{timed_out}) {
> > Warning("$str TIMED OUT (failed)\n");
> > } else {
> > Warning("$str FAILED\n");
> > }
> >
> > Are you talking about some other output? Or are you asking for
> > something in (parentheses)?
>
> Sorry, I wasn't clear. The current output for each test in the debug file
> usually includes a line "test_result: X" with X replaced by a number.
> However, for tests that fail outright, this line is missing. This missing
> line happened to correspond to the tests that had a newline in the result
> message that I discussed (snipped) above.
>
> Please don't put in the parentheses things. That was just me commenting
> on which number meant what.
>
>
> > If you're in the middle of revamping your parser to match the MTT 2.0
> > output, I might suggest that it might be far easier to just
> > incorporate your desired output into MTT itself, for two reasons:
> >
> > 1. the debug output can change at any time; it was meant to be for
> > debugging, not necessarily for screen scraping.
>
> Point taken.
>
> > 2. there would be no need for screen scraping/parsing; you would have
> > the data immediately available and all you have to do is output it
> > into the format that you want. We should be able to accommodate
> > whatever you need via an MTT Reporter plugin. I'm guessing this
> > should be pretty straightforward...?
>
> Where can I find some documentation for or examples of a plugin?

They're all in this directory:

https://svn.open-mpi.org/trac/mtt/browser/trunk/lib/MTT/Reporter/

You probably want to look at these:

https://svn.open-mpi.org/trac/mtt/browser/trunk/lib/MTT/Reporter/TextFile.pm
https://svn.open-mpi.org/trac/mtt/browser/trunk/lib/MTT/Reporter/Email.pm
https://svn.open-mpi.org/trac/mtt/browser/trunk/lib/MTT/Reporter/INIFile.pm

-Ethan

>
> > --
> > Jeff Squyres
> > Server Virtualization Business Unit
> > Cisco Systems
>
>
> --
> Tim Mattox - http://homepage.mac.com/tmattox/
> tmattox_at_[hidden] || timattox_at_[hidden]
> I'm a bright... http://www.the-brights.net/
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users