Re: [MTT devel] Best way to run ftb_database_server and ftb_agent
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). On Nov 8, 2010, at 5:16 PM, DongInn Kim wrote: > 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.6.2] / [platform] > *** WARNING: Unable to find MPI details section for [MPI Install: platform; >skipping > *** Run test phase complete >>> Phase: Test Run > Started: Mon Nov 8 17:10:30 2010 > Stopped: Mon Nov 8 17:10:31 2010 > Elapsed: 00:00:01 0.02u 0.06s > Total elapsed: 00:00:01 0.02u 0.06s >>> Phase: Trim > Started: Mon Nov 8 17:10:31 2010 > Stopped: Mon Nov 8 17:10:31 2010 > Elapsed: 00:00:00 0.00u 0.00s > Total elapsed: 00:00:01 0.02u 0.06s > *** Reporter finalizing > *** Reporter finalized > > > Here is the entry in the new ftb.ini file. > #-- > > > [MPI Details: platform] > > # Need a before_any_exec step to test all the FTB example tests > > before_any_exec = < install_dir=&test_prefix_pretty() > > ftb_server_daemon="$install_dir/sbin/ftb_database_server" > > ftb_agent_daemon="$install_dir/sbin/ftb_agent" > > $ftb_server_daemon & > $ftb_agent_daemon > EOF > > after_all_exec = < > ftb_db_pid=`pgrep ftb_database_server` > kill $ftb_db_pid > ftb_agent_pid=`pgrep ftb_agent` > > kill $ftb_agent_pid > EOT > > #-- > > I have tried to replace "platform" with "FTB" in "[MPI Details: platform]" > but it still did not work. > > Any helps on this? > > Regards, > > > On 11/8/10 3:42 PM, Jeff Squyres wrote: >> 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_exec -- run after after every single exec (include all variants) >> after_all_exec -- run after all tests in a given Test Run section have >> completed >> >> So you can use the before_any_exec / after_all_exec to launch the daemons >> once at the beginning and then take them down, or you can use >> before_each_exec / after_each_exec to launch the daemons before each test >> and then take them down at the end of that test. >> >> I'm assuming that the *each* variants will cause your tests to run much >> slower. >> >> I see that we don't have an MPI Details section on the wiki describing these >> parameters. Sorry! :-( >> >> > > > -- > - DongInn > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [MTT devel] Best way to run ftb_database_server and ftb_agent
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.6.2] / [platform] *** WARNING: Unable to find MPI details section for [MPI Install: platform; skipping *** Run test phase complete >> Phase: Test Run Started: Mon Nov 8 17:10:30 2010 Stopped: Mon Nov 8 17:10:31 2010 Elapsed: 00:00:01 0.02u 0.06s Total elapsed: 00:00:01 0.02u 0.06s >> Phase: Trim Started: Mon Nov 8 17:10:31 2010 Stopped: Mon Nov 8 17:10:31 2010 Elapsed: 00:00:00 0.00u 0.00s Total elapsed: 00:00:01 0.02u 0.06s *** Reporter finalizing *** Reporter finalized Here is the entry in the new ftb.ini file. #-- [MPI Details: platform] # Need a before_any_exec step to test all the FTB example tests before_any_exec = < 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_exec -- run after after every single exec (include all variants) > after_all_exec -- run after all tests in a given Test Run section have > completed > > So you can use the before_any_exec / after_all_exec to launch the daemons > once at the beginning and then take them down, or you can use > before_each_exec / after_each_exec to launch the daemons before each test and > then take them down at the end of that test. > > I'm assuming that the *each* variants will cause your tests to run much > slower. > > I see that we don't have an MPI Details section on the wiki describing these > parameters. Sorry! :-( > > -- - DongInn
Re: [MTT devel] Best way to run ftb_database_server and ftb_agent
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_exec -- run after after every single exec (include all variants)
after_all_exec -- run after all tests in a given Test Run section have completed
So you can use the before_any_exec / after_all_exec to launch the daemons once
at the beginning and then take them down, or you can use before_each_exec /
after_each_exec to launch the daemons before each test and then take them down
at the end of that test.
I'm assuming that the *each* variants will cause your tests to run much slower.
I see that we don't have an MPI Details section on the wiki describing these
parameters. Sorry! :-(
On Nov 7, 2010, at 10:05 AM, DongInn Kim wrote:
> 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_path' => undef,
> 'mpi_name' => 'ftb-nightly-trunk',
> 'compiler_version' => 'unknown',
> 'pid' => 23511,
> 'elapsed_iters' => '0.02',
> 'bindir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/installs/c1aD/install/bin',
> 'merge_stdout_stderr' => 0,
> 'elapsed_user' => '0',
> 'unsetenv' => undef,
> 'cxx_bindings' => '0',
> 'description' => undef,
> 'f90_bindings' => '0',
> 'exit_status' => undef,
> 'libdir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/installs/c1aD/install/lib',
> 'mpi_get_simple_section_name' => 'ftb-nightly-trunk',
> 'elapsed_real' => 0,
> 'f77_bindings' => '0',
> 'source_dir' => 'ftb-0.6.2',
> 'mpi_version' => '0.6.2',
> 'sym_link_name' => 'ftb-nightly-trunk--platform--0.6.2',
> 'c_bindings' => 1,
> 'full_section_name' => 'ftb install: platform',
> 'vpath_mode' => 0,
> 'elapsed_children_system' => '0.02',
> 'timed_out' => 0,
> 'refcount' => 0,
> 'env_modules' => undef,
> 'elapsed_children_user' => '0',
> 'start_benchmark' => bless( [
>1289110689,
>'0.4',
>'0.12',
>'2.48',
>'1.8',
>0
> ], 'Benchmark' ),
> 'version_dir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/installs/c1aD',
> 'build_version_dir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/ftb-install/ohiy',
> 'ftb_get_simple_section_name' => 'ftb-nightly-trunk',
> 'ftb_version' => '0.6.2',
> 'result_message' => 'Success',
> 'append_path' => undef,
> 'configure_arguments' => '"CFLAGS=-g -pipe" --enable-debug ',
> 'installdir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/installs/c1aD/install',
> 'test_result' => 1,
> 'compiler_name' => 'unknown',
> 'build_dir' =>
> '/nfs/rinfs/san/homedirs/ftbteam/ftt-runs/odin/20101107-Nightly/pb_0/ftb-install/ohiy/src/ftb-0.6.2',
> 'simple_section_name' => 'platform',
> 'setenv' => undef,
> 'start_timestamp' => 1289110690,
> 'stop_benchmark' => bless( [
> 1289110689,
> '0.4',
> '0.12',
> '2.5',
> '1.82',
> 0
> ], 'Benchmark' )
>};
>
> DB<34>
>
>
> The ini files that I used are
> general_ini_base = $HOME/iu-ftt/odin/etc/general
>
> general_ini = generic-subs2.config
>
> specific_ini_base = $HOME/iu-ftt/etc/ftt2
> specific_ini = BEGIN
> g-br-trunk,i-32gccFT,ftb
> END
>
> It seems that mtt does not pickup the entries that I put in
> generic-sub2.config.
> #--
> #--
>
> [FTB Details: ftb]
> exec = ./run-ftb-tests.pl -test &test_executable()
>
>
> #--
> #
