On Mar 1, 2007, at 2:03 PM, Ethan Mallove wrote:
Good point. If the mtt client couldn't contact the
database, then Test Builds and Test Runs will not contain
their required mpi_install and test_build ID's (you'll see
FOREIGN KEY constraint errors in the output).
Not being able to contact the d
Good point. If the mtt client couldn't contact the
database, then Test Builds and Test Runs will not contain
their required mpi_install and test_build ID's (you'll see
FOREIGN KEY constraint errors in the output).
Not being able to contact the database is an Abort condition
at startup, but we nee
Ethan -
Will this work to submit results for phases that don't have
corresponding prior phase IDs?
I.e., if I did an MPI install, Test build, and Test run phases -- and
none of them were successfully submitted -- will submitted the test
build/run data work, since they don't have a corresp
I just added a client/mtt-submit script to the mtt/trunk SVN
repository which will help you. You'll need to use it like
this:
$ client/mtt-submit -f '/directory/where/results/are/*.txt' -g -u cisco -p
/directory/where/results/are/ is specified in your INI file
as mttdatabase_debug_filename.
C
That's awesome. Good work :)
-- Josh
On Mar 1, 2007, at 11:59 AM, Ethan Mallove wrote:
Folks,
If some of you hadn't already noticed, reports (see
http://www.open-mpi.org/mtt/) on Test Runs have been taking
an upwards of 5-7 minutes to load as of late. This was due
in part to some database de
Folks,
If some of you hadn't already noticed, reports (see
http://www.open-mpi.org/mtt/) on Test Runs have been taking
an upwards of 5-7 minutes to load as of late. This was due
in part to some database design issues (compounded by the
fact that we now have nearly 3 million test results
archived,
We had a proxy server fail during the night and may have had some
results get lost. Jeff asked me to check for existence of a
resubmission script - is there one, and if so where is it?
--
Bill D'Amico
bdam...@cisco.com
Server virtualization Business Unit
