Run the cgpt tests in a separate directory.

tests/common.sh

 #!/bin/bash
 
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Determine script directory.
-if [[ $0 == '/'* ]];
-then
-  SCRIPT_DIR="`dirname $0`"
-elif [[ $0 == './'* ]];
-then
-  SCRIPT_DIR="`pwd`"
-else
-  SCRIPT_DIR="`pwd`"/"`dirname $0`"
-fi
+SCRIPT_DIR=$(dirname $(readlink -f "$0"))

[vb, 2010/08/19 23:15:35]

This is a noop change, right? 

It of course is a nice cleanup, but gnerally speaking should be a separate cl.

[gauravsh, 2010/08/19 23:34:47]

FYI, The original complicated logic for determining script directory was added
by me because of the way autotest was invoking testing scripts - and yes it is
ugly. As it turns out, the only way to determine the script calling directory
that works in all cases is to use lsof. :)

Anyway, this was probably overkill and since we are now moving all autotests
into their associated git repositories, maybe needed any more.

Bill: Have you made sure this simplified logic handles the both of the
following:

./run_some_test

(while in some other directory)
/path/to/test/dir/run_some_test.sh

[Bill Richardson, 2010/08/19 23:59:34]

Yes. That's why I added it in the first place. The old way didn't work if I
started in the parent directory and said "./tests/run_cgpt_tests.sh
./build/cgpt/cgpt"

 
 ROOT_DIR="$(dirname ${SCRIPT_DIR})"
 BUILD_DIR="${ROOT_DIR}/build"
 UTIL_DIR="${BUILD_DIR}/utility"
 TEST_DIR="${BUILD_DIR}/tests"
 TESTKEY_DIR=${SCRIPT_DIR}/testkeys
 TESTCASE_DIR=${SCRIPT_DIR}/testcases
 TESTKEY_SCRATCH_DIR=${TEST_DIR}/testkeys
 
 if [ ! -d ${TESTKEY_SCRATCH_DIR} ]; then
@@ skipping 21 matching lines @@
 function error {
   echo -e "${COL_RED}ERROR: $*${COL_STOP}" 1>&2
   exit 1
 }
 
 function check_test_keys {
   [ -d ${TESTKEY_DIR} ] || \
     error "You must run gen_test_keys.sh to generate test keys first."
 }