On Fri, Aug/10/2007 01:02:16PM, Jeff Squyres wrote:
> On Aug 10, 2007, at 10:14 AM, Ethan Mallove wrote:
>
> > Do we still need to write out an INI file after each MPI
> > Install and Test Build? I thought we're using .dump
> > files instead? (I noticed this because it seemed to be
> > taking a few minutes to write the INI file after
> > building the intel tests.)
>
> IIRC, those are test-build-specific files and down far
> deep in the scratch tree. The intent was to capture
> *everything* there (including all of stdout/stderr) in
> case there was something valuable there that we didn't
> capture sending up to the DB.
>
> However, I could see how it wouldn't be too valuable these
> days.
>
> How about turning it off, but leaving an option in the
> [MTT] section to re-enable it if we ever need it again?
>
Looking a little closer, there are inconsistencies in what's
going to the saved .dump and .ini files:
Test Run .dump (split up by variants):
* Everything (including stdout/stderr)
Test Run .ini:
* Nothing
Test Build .dump:
* Everything (except stdout/stderr)
Test Build .ini (split up by test suites):
* Everything execept database serials, mpi_name,
and environment (e.g., prepend_path, env_module, etc)
MPI Install .ini:
* Nothing
MPI Install .dump:
* Everything
How about we put *everything* in the .dump files, while
offering to also save *everything* in INI files in the [MTT]
section? Though Perl-Dumper is only slightly less
human-readble than INI.
These are also a little confusing:
save_stdout_on_success
stderr_save_lines
Don't we want these instead broken up into two: inifile and
mttdatabase? So a user might choose to save more or less on
their disk than to the database?
save_stdout_on_success_to_mttdatabase
stderr_save_lines_to_mttdatabase
save_stdout_on_success_to_inifile
stderr_save_lines_to_inifile
-Ethan
> --
> Jeff Squyres
> Cisco Systems
>
> _______________________________________________
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
