Re: [MTT devel] Best way to run ftb_database_server and ftb_agent

2010-11-09 Thread Jeff Squyres 
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 that are used by subsequent phases.

> 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.

What exactly do you have in your ini file again for these fields?

I have this in an old ini file -- it *used* to work (when launching MPICH2 and 
Intel MPI jobs through MTT):

before_any_exec = < $file
# Add localhost if it's not in there (e.g., srun -A)
local=`grep $h $file`
touch /tmp/mtt-mpiexec-options.$SLURM_JOBID
if test "$local" = ""; then
   echo $h >> $file
   echo -nolocal > /tmp/mpiexec-options.$SLURM_JOBID
fi
num=`wc -l $file | awk '{ print $1 }'`
mpdboot -n $num -r ssh --verbose --file=$file
mpdtrace
rm -f $file
EOF

-- 
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

2010-11-09 Thread DongInn Kim 
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 = { 
  'program_dir' => '/u/ftbteam/projects/mtt/client',
  'after_all_exec' => [ 
'ftb_db_pid=`pgrep ftb_database_server`',
'kill $ftb_db_pid',
'ftb_agent_pid=`pgrep ftb_agent`',
'kill $ftb_agent_pid'
  ],
  'before_any_exec' => [ 
 'install_dir=_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'
   ],
  'program_name' => '/u/ftbteam/projects/mtt/client/ftt',
  'ini_section_name' => 'platform',
  'ini_name' => 
'/u/ftbteam/ftt-runs/odin/20101108-Nightly/ini/g-br-trunk_i-32gccFT_ftb-gen'
};

It seems that entries of before_** and after_** are filled in to the steps to 
run but it could not run because of the malformed syntax.
So, I removed the entries and then just "touch /tmp/foo" in before_** and 
after_** but it did not create the empty file /tmp/foo and I got the following 
errors in the perl debug mode.
*** ERROR: Module aborted: MTT::Test::Specify::Simple:Specify: Bizarre copy
of ARRAY in leave at
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Values.pm line
118,  line 63.
 at /nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Messages.pm line 122
MTT::Messages::Abort('Module aborted: 
MTT::Test::Specify::Simple:Specify: Bizarre c...') called at 
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Messages.pm line 85
MTT::Messages::Error('Module aborted: 
MTT::Test::Specify::Simple:Specify: Bizarre c...') called at 
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Module.pm line 52
MTT::Module::Run('MTT::Test::Specify::Simple', 'Specify', 
'Config::IniFiles=HASH(0x19dfea0)', 'test run: ftb', 'HASH(0x19ebba0)', 
'HASH(0x19e4940)', 'HASH(0x19df600)') called at 
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Test/Specify.pm line 24
MTT::Test::Specify::Specify('Simple', 
'Config::IniFiles=HASH(0x19dfea0)', 'test run: ftb', 'HASH(0x19ebba0)', 
'HASH(0x19e4940)', 'HASH(0x19df600)') called at 
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Test/Run.pm line 552
MTT::Test::Run::_do_run('Config::IniFiles=HASH(0x19dfea0)', 'test run: 
ftb', 'HASH(0x19ebba0)', 'HASH(0x19dfdf0)', 'HASH(0x19e4940)', 
'/u/ftbteam/ftt-runs/odin/20101109-Nightly/pb_0/installs', 
'/u/ftbteam/ftt-runs/odin/20101109-Nightly/pb_0/test_runs', 'undef') called at 
/nfs/rinfs/san/homedirs/ftbteam/projects/mtt/lib/MTT/Test/Run.pm line 200
MTT::Test::Run::Run('Config::IniFiles=HASH(0x19dfea0)', 
'Config::IniFiles=HASH(0x19ba940)', 
'/u/ftbteam/ftt-runs/odin/20101109-Nightly/pb_0/installs', 
'/u/ftbteam/ftt-runs/odin/20101109-Nightly/pb_0/test_runs', 'undef') called at 
/u/ftbteam/projects/mtt/client/ftt line 557

Can you please help this out?

Regards,   

On 11/8/10 5:27 PM, Jeff Squyres wrote:
> 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
>> *** Repo