I wonder if reporter.php can help out some here. IIRC, a
major advantage of your parsing scripts was to see results
of individual MTT invocations, and characteristics of
invocations that reporter.php wasn't able to show.
reporter.php now keeps track of results ''by invocation''
much more systematically then before. Could you give me a
use case of what you want you want in a report? (Or point me
to some examples in ompi-tests/trunk/iu/mtt - Josh had some
mock ups of your reports, but I lost track of them.)
On Fri, Jan/19/2007 11:50:54AM, 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