Open MPI logo

MTT Devel Mailing List Archives

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

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-01-19 12:33:49


To follow up for those following this on the mailing list...

I chatted with Tim about this on the phone a bit. It turns out that
the IU parser is not parsing the debugging MTT output, but rather the
text reporter output. They do this because they do a whole bunch of
MTT runs and then parse *all* the text reporter output to make a
single e-mail report.

What happened was that we changed some of the field names in MTT, so
the IU parser wasn't finding the fields that they wanted.

Additionally, I just filed ticket #191 -- we're apparently somehow
skipping fields in the TextReporter (and possibly elsewhere) that
have a "0" value. That needs to be fixed.

On Jan 19, 2007, at 11:50 AM, Jeff Squyres wrote:

> On Jan 19, 2007, at 8:55 AM, Tim Mattox wrote:
>
>> 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.
>
> I forgot to mention -- let me know where you land on the whole
> "continue to parse debug output" vs. "write an MTT reporter" issue.
> If you write a new reporter, this particular issue ^^ is moot.
>
> --
> Jeff Squyres
> Server Virtualization Business Unit
> Cisco Systems
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

-- 
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems