Looks good. Thanks for doing this. I did need the following patch though to correct a capitalization problem...
Tim Index: lib/MTT/Reporter/ParsableTextfile.pm =================================================================== --- lib/MTT/Reporter/ParsableTextfile.pm (revision 742) +++ lib/MTT/Reporter/ParsableTextfile.pm (working copy) @@ -10,7 +10,7 @@ # $HEADER$ # -package MTT::Reporter::ParsableTextFile; +package MTT::Reporter::ParsableTextfile; use strict; use Cwd; On Tuesday 10 July 2007 04:40:40 pm Ethan Mallove wrote: > Done. > > I brought it back as "ParsableTextfile" in both the trunk > and ompi-core-testers. You'll just have to do two things in > your INI file: > > * Change "module = Textfile" to "module = ParsableTextfile" > * Rename "textfile_" params to "parsabletextfile_" params > > Let me know if you run into any other issues with this. > > -Ethan > > On Tue, Jul/10/2007 02:27:27PM, Tim Prins wrote: > > Hmm, the INI file reporter does not seem to work for me. For the test > > results I only get the information about the last test run. > > > > Anyways, I like the idea of pulling the data directly in from perl output > > but just don't have the time to mess with it right now. For me bringing > > back the old reporter would be easiest for the time being. However, I > > also need the following patch applied to resurect a couple output fields > > that were removed which we need: > > > > Index: lib/MTT/Test/Analyze/Correctness.pm > > =================================================================== > > --- lib/MTT/Test/Analyze/Correctness.pm (revision 737) > > +++ lib/MTT/Test/Analyze/Correctness.pm (working copy) > > @@ -53,6 +53,8 @@ > > > > test_name => $run->{name}, > > command => $run->{cmd}, > > + test_build_section_name => > > $run->{test_build_simple_section_name}, + > > np => $run->{np}, > > exit_value => > > MTT::DoCommand::exit_value($results->{exit_status}), exit_signal => > > MTT::DoCommand::exit_signal($results->{exit_status}), Index: > > lib/MTT/MPI/Install.pm > > =================================================================== > > --- lib/MTT/MPI/Install.pm (revision 737) > > +++ lib/MTT/MPI/Install.pm (working copy) > > @@ -505,6 +505,8 @@ > > my $report = { > > phase => "MPI Install", > > > > + mpi_install_section_name => $config->{simple_section_name}, > > + > > bitness => $config->{bitness}, > > endian => $config->{endian}, > > compiler_name => $config->{compiler_name}, > > > > > > Thanks, > > > > Tim > > > > On Tuesday 10 July 2007 11:46:34 am Ethan Mallove wrote: > > > Whoops! I didn't realize anyone was using that Textfile > > > module. We can resurrect that if you'd like (call it > > > ParseableTextfile). > > > > > > There's also the INIFile Reporter. That might be your best > > > bet, since there's a Config::INIFiles CPAN module. (Your > > > wrappers are in Perl, right?) Though wouldn't it be even > > > easier if there were a PerlDumper Reporter module so you > > > could read in the data *directly* to your Perl wrappers? > > > Your wrapper would do no parsing then. E.g., > > > > > > open(FILE, "< $file"); > > > undef $/; > > > $mtt_results = <FILE>; > > > > > > -Ethan > > > > > > On Mon, Jul/09/2007 06:07:51PM, Tim Prins wrote: > > > > Hi, > > > > > > > > With the new version of MTT, the textfile report file > > > > format changed to a more human readable format. Since we > > > > here at IU use a script to parse this, it presents a bit > > > > of a problem. I can update our script, but was wondering > > > > how stable this new output format is. > > > > > > > > If it will not be very stable, I was wondering if the > > > > developers would consider adding a parseable textfile > > > > output module. The easiest thing to do for this would be > > > > to just import the old textfile module as a new parseable > > > > module. I have tried this and it seems to work fine, > > > > however there may be problems with this that I am unaware > > > > of. > > > > > > > > I can deal with this either way, but just thought it might > > > > make things easier to have a parseable format that is > > > > relatively static, and a human readable format that can be > > > > tweaked for useability as time goes by. > > > > > > > > Thanks, > > > > > > > > Tim > > > > _______________________________________________ > > > > mtt-users mailing list > > > > mtt-us...@open-mpi.org > > > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > > > > > > _______________________________________________ > > > mtt-users mailing list > > > mtt-us...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > > > > _______________________________________________ > > mtt-users mailing list > > mtt-us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > > _______________________________________________ > mtt-users mailing list > mtt-us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users