From: Ethan Mallove (ethan.mallove_at_[hidden])
Date: 2007-01-19 15:25:44
Just remembered where I put the examples Josh sent me :)
Here are some attempts at getting reporter.php to do similar
things to your custom report(s).
Summary page:
http://www.open-mpi.org/~emallove/mtt/reporter.php?do_redir=74
Display test name, np, and duration (for ''intel'' tests
only):
http://www.open-mpi.org/~emallove/mtt/reporter.php?do_redir=75
Clicking the down arrow to the right of the duration header
sorts the results, ''longest'' running time first:
http://www.open-mpi.org/~emallove/mtt/reporter.php?do_redir=76
Next, it looks like you want to split out 32/64-bit results.
Do they have identifiable configure arguments? Sun has two
sets of configure arguments ('-xarch=v8' for 32 and
'-xarch=v9' for 64), which can be reported on like so:
http://www.open-mpi.org/~emallove/mtt/reporter.php?do_redir=66
-Ethan
On Fri, Jan/19/2007 01:57:16PM, Ethan Mallove wrote:
> Tim,
>
> 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.)
>
> -Ethan
>
>
> 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
> > mtt-users_at_[hidden]
> > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users