File: reg_test_template

package info (click to toggle)
gcc-avr 1%3A5.4.0%2BAtmel3.6.1-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 589,832 kB
  • sloc: ansic: 2,775,567; ada: 756,757; cpp: 723,977; f90: 117,673; asm: 66,896; makefile: 62,755; xml: 44,466; sh: 29,549; exp: 23,315; objc: 15,216; fortran: 10,901; pascal: 4,185; python: 4,093; perl: 2,969; awk: 2,811; ml: 2,385; cs: 879; yacc: 316; lex: 198; haskell: 112; lisp: 8
file content (41 lines) | stat: -rwxr-xr-x 1,195 bytes parent folder | download | duplicates (12)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
#! /bin/sh

# Template for the test script specified for REG_TEST.

# Run the test case for a regression search.  The argument is the date
# of the sources.  The return value is 1 if the binary search should
# continue with later dates, 0 if it should continue with earlier
# dates.

DATE="${1}"

# Specify the PR number and the directory where the test should be run.
PR=xxxx
DIR=xxxx

LOG_DATE="`echo ${DATE} | sed 's/[-: ]/_/g'`"
LOG="${PR}.${LOG_DATE}.out"

echo "`date`  running test for PR ${PR}"
cd ${DIR}

# Compile the test case with whatever options are needed to trigger the
# error.

<compiler_to_run> <options> ${PR}.<x> > ${LOG} 2>&1

# Some tests will require additional commands to determine whether the
# test passed or failed, such as grepping compiler output for a
# particular message, or running the test and possibly comparing its
# output with the expected output.

xxxxx

# The return value depends on whether the last command is expected to be
# zero or nonzero for a passing test, and whether we're looking for a
# regression or for the patch that fixed the bug.

# Return 1 to continue the search with later dates, 0 for earlier dates.

test $? -eq 0 && exit 1
exit 0