[Ltp-cvs] ltp/testcases/realtime/func/pi_perf run_auto.sh,1.1,1.2

[Subrata <sub...@us...>]

Update of /cvsroot/ltp/ltp/testcases/realtime/func/pi_perf
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26900/ltp/testcases/realtime/func/pi_perf

Modified Files:
	run_auto.sh 
Log Message:
Profiled Tests:
Basically this was done to enhance the pass/fail criteria usage and allow the user to setup tests configurations according to specific needs. Imagine a test series that may validate a hardware for some latencies (case #1) while another series would validate other criteria (case #2). The same test used in situation #1 will not have the same configuration (arguments) in situation #2. Scripting has to be done for this to achieve. The profile system does this for you. You just have to configure. Not only pass/fail criteria can be set since the profile system simply runs command lines defined in profiles. So any argument can be choosen. ie: a profile can define criteria for tests with or without saving statistics (-s) or simulate jvm (-j). A profile comes as a single file so it is easy to copy from a test machine to another. With this patch, profiles can be used either for test global run (./run.sh) or for an individual directory (./run_auto.sh). For more information, read doc/AUTOMATED_RUN.
This patch is intentionnally global as splitting changes would not make sense. This includes:
- changes of scripts for automated tests to feature profiles
- individual changes for tests using automation
- a default profile (to be used as an example)
- documentation writing/modifying.
Signed-off-by: Gilles Carry <gil...@bu...>,
Reviewed-by: Ankita Garg <an...@in...>.


Index: run_auto.sh
===================================================================
RCS file: /cvsroot/ltp/ltp/testcases/realtime/func/pi_perf/run_auto.sh,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** run_auto.sh	26 Dec 2007 11:11:50 -0000	1.1
--- run_auto.sh	22 May 2008 12:03:14 -0000	1.2
***************
*** 1,4 ****
--- 1,7 ----
  #! /bin/bash
  
+ profile=${1:-default}
+ 
+ cd $(dirname $0) # Move to test directory
  if [ ! $SCRIPTS_DIR ]; then
          # assume we're running standalone
***************
*** 8,10 ****
  source $SCRIPTS_DIR/setenv.sh
  
! $SCRIPTS_DIR/run_c_files.sh "pi_perf"
--- 11,14 ----
  source $SCRIPTS_DIR/setenv.sh
  
! # Warning: tests args are now set in profiles
! $SCRIPTS_DIR/run_c_files.sh $profile pi_perf