On Nov 9, 2010, at 1:00 AM, DongInn Kim wrote:
> No, I did not know that it should be added in the MPI Get phase.
You have to call all the phases, even if they don't "do" anything. That's why
we have no-op / alreadyinstalled versions of plugins, for example. Each phase
sets up data structures
No, I did not know that it should be added in the MPI Get phase.
OK, I tried to add it the MPI Get phase and mpi_details are recognized but I
could not have "Test Run" phase run the scripts in before_any_exec and
after_all_exec.
DB<25> p Dumper($self->{v}{$sect})
$VAR1 = {
'pro
Are you executing an MPI Get section?
I believe that the mpi_details section is filled in via the MPI Get phase and
then propagated down through all the other phases (i.e., each of the other
phases looks a the way back to their corresponding mpi get phase to find
the mpi_details value).
O
Jeff, thank you.
BTW, I have looked at the ompi-core-perf-testing.ini file which seems to have
used the mpi detail sections and I tried to use it in our ftb.ini file but I
still get the same warning message.
*** Test Run phase starting
>> Test Run [ftb]
>> Running with [ftb-nightly-trunk] / [0.
Sorry for jumping in late -- been swamped recently...
In the MPI details section, there's 4 fields that should let you do what you
want.
before_any_exec -- run once before all the tests in a given Test Run
before_each_exec -- run once before every single exec (including all variants)
after_each_
Hi Josh,
Hmm, I still can not define "mpi_details" in the ini file. Is there something
wrong with my ini file?
DB<32> p $mpi_install->{mpi_details}
DB<33>
DB<33> p Dumper($mpi_install)
$VAR1 = {
'ftb_get_full_section_name' => 'ftb get: ftb-nightly-trunk',
'prepend_pat
Josh, thanks but actually I don't know how to set the base directory of the
test suite in the Test Get/Build phase. Is it setup in the ini file or
somewhere? and how?
Regards,
On 11/5/10 11:32 AM, Joshua Hursey wrote:
>
> On Nov 5, 2010, at 10:11 AM, DongInn Kim wrote:
>
>> Josh, I have anoth
On Nov 5, 2010, at 10:11 AM, DongInn Kim wrote:
> Josh, I have another question.
> How can mtt find the script to run?
>>> exec = ./run-cr-correctness.pl -test ...
>
> I can write a similar script like run-correctness.pl but if I put my
> script(e.g., run-ftb-tests.pl) to ftb-tests/iu/ftt/ftb/,
On Fri, Nov 5, 2010 at 9:01 AM, DongInn Kim wrote:
> Hi Josh,
> > Do you need to restart the FTB daemons before every test, or just start
> them once before running an entire test suite?
> I believe that the daemon needs to run once before running an entire test
> set. Abhishek, can you confirm?
Josh, I have another question.
How can mtt find the script to run?
>> exec = ./run-cr-correctness.pl -test ...
I can write a similar script like run-correctness.pl but if I put my
script(e.g., run-ftb-tests.pl) to ftb-tests/iu/ftt/ftb/, how can I make mtt
recognize this path and file?
Regards,
Hi Josh,
> Do you need to restart the FTB daemons before every test, or just start them
> once before running an entire test suite?
I believe that the daemon needs to run once before running an entire test set.
Abhishek, can you confirm?
I would follow your suggestion(i.e., add the script to run
DongInn,
Do you need to restart the FTB daemons before every test, or just start them
once before running an entire test suite?
Adding another phase is pretty involved (will likely require changes to every
piece of MTT - client, database, reporter), so I would suggest doing something
like thi
Hi,
Is there any way to put some lines to the mtt ini file to run the FTB
daemons(ftb_database_server and ftb_agent)?
Should we make another "FTB Run" phase after "FTB Install" or run the two
daemons inside "Test run" but run the daemons before running the test scripts?
I think either way would
13 matches
Mail list logo
