| 1 |
#! /bin/sh |
| 2 |
|
| 3 |
# Template for the test script specified for REG_TEST. |
| 4 |
|
| 5 |
# Run the test case for a regression search. The argument is the date |
| 6 |
# of the sources. The return value is 1 if the binary search should |
| 7 |
# continue with later dates, 0 if it should continue with earlier |
| 8 |
# dates. |
| 9 |
|
| 10 |
DATE="${1}" |
| 11 |
|
| 12 |
# Specify the PR number and the directory where the test should be run. |
| 13 |
PR=xxxx |
| 14 |
DIR=xxxx |
| 15 |
|
| 16 |
LOG_DATE="`echo ${DATE} | sed 's/[-: ]/_/g'`" |
| 17 |
LOG="${PR}.${LOG_DATE}.out" |
| 18 |
|
| 19 |
echo "`date` running test for PR ${PR}" |
| 20 |
cd ${DIR} |
| 21 |
|
| 22 |
# Compile the test case with whatever options are needed to trigger the |
| 23 |
# error. |
| 24 |
|
| 25 |
<compiler_to_run> <options> ${PR}.<x> > ${LOG} 2>&1 |
| 26 |
|
| 27 |
# Some tests will require additional commands to determine whether the |
| 28 |
# test passed or failed, such as grepping compiler output for a |
| 29 |
# particular message, or running the test and possibly comparing its |
| 30 |
# output with the expected output. |
| 31 |
|
| 32 |
xxxxx |
| 33 |
|
| 34 |
# The return value depends on whether the last command is expected to be |
| 35 |
# zero or nonzero for a passing test, and whether we're looking for a |
| 36 |
# regression or for the patch that fixed the bug. |
| 37 |
|
| 38 |
# Return 1 to continue the search with later dates, 0 for earlier dates. |
| 39 |
|
| 40 |
test $? -eq 0 && exit 1 |
| 41 |
exit 0 |