I'm assuming that this is a per-user kind of setting, right? (e.g., stored in a cookie)

It looks promising, but I'd put better titles on the two screens. E.g., I'd call this results filtering, or somesuch.


On May 21, 2007, at 3:42 PM, Ethan Mallove wrote:

I have something to help filter out (in reporter.php) old
known OMPI failures, though this feature is still in an
embryonic stage.

E.g., here's a link that shows *all* of Sun's recent Test
Run failures.

http://www.open-mpi.org/~emallove/mtt_/reporter.php?do_redir=199

If I don't care to sift through all the SPARC "alignment"
errors that are already in our bug tracking system, I can
add that failure here at the below link.

http://www.open-mpi.org/~emallove/mtt_/track-failures/?screen=Insert

The HTML form would like something like this:

  Field: "Hardware" Value: _sun4u_
  Field: "Stdout"   Value: _invalid address alignment_
  (The remaining 8 rows of the form would be left blank)

One can see the entire database of failures in
"Delete Mode". E.g.,

http://www.open-mpi.org/~emallove/mtt_/track-failures/?screen=Delete

E.g., now if I don't care to see the alignment errors, I can
checkbox the "Filter tracked failures" box in Preferences.
VoilĂ :

http://www.open-mpi.org/~emallove/mtt_/reporter.php?do_redir=200

Thoughts?

-Ethan
_______________________________________________
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


--
Jeff Squyres
Cisco Systems


Reply via email to