view libtests/run-tests.sh @ 412:223eda8408e1 api-inversion

Fix the last compiler warning. Bah. A 26-line comment to explain a one-line change will not do any good for the code deletion metric of productivity. However, I have learnt something today: specifically, the arithmetic type conversion rules in C. Wow. I had been beginning to think that C programming wasn't so bad after all: simple, clean semantics, and very little going on under the hood; nothing there to help the programmer, but nothing much to actively get in the way. And then I spend an hour on this.
author mas01cr
date Thu, 11 Dec 2008 17:51:03 +0000
parents cd63493c32a9
children 4cb6c611f812 342822c2d49a
line wrap: on
line source
#! /bin/bash

AUDIODB=../../${EXECUTABLE:-audioDB}
export AUDIODB

if [ -x ${AUDIODB#../} ]; then 
  :
else 
  echo Cannot execute audioDB: ${AUDIODB#../}
  exit 1
fi

if [ "$1" = "--full" ]; then
  pattern="[0-9][0-9][0-9][0-9]*"
else
  pattern="[0-8][0-9][0-9][0-9]*"
fi

for file in ${pattern}; do
  if [ -d ${file} ]; then
    if [ /bin/true ]; then
      echo -n Running test ${file}
      if [ -f ${file}/short-description ]; then
        awk '{ printf(" (%s)",$0) }' < ${file}/short-description
      fi
      echo -n :
      (cd ${file} && make -f ../libtest.mk >/dev/null 2>&1 && ./test1 > test.out 2> test.err && exit 104)
      EXIT_STATUS=$?
      if [ ${EXIT_STATUS} -eq 14 ]; then
        echo " n/a."
      elif [ ${EXIT_STATUS} -ne 104 ]; then
        echo " failed (exit status ${EXIT_STATUS})."
        FAILED=true
      else
        echo " success."
      fi
    else
      echo Skipping test ${file}
    fi
  fi
done

if [ -z "${FAILED}" ]; then
  exit 0
else
  exit 1
fi