diff options
author | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
---|---|---|
committer | upstream source tree <ports@midipix.org> | 2015-03-15 20:14:05 -0400 |
commit | 554fd8c5195424bdbcabf5de30fdc183aba391bd (patch) | |
tree | 976dc5ab7fddf506dadce60ae936f43f58787092 /contrib/reghunt/date_based/reg_test_template | |
download | cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.bz2 cbb-gcc-4.6.4-554fd8c5195424bdbcabf5de30fdc183aba391bd.tar.xz |
obtained gcc-4.6.4.tar.bz2 from upstream website;upstream
verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.
downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.
if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.
Diffstat (limited to 'contrib/reghunt/date_based/reg_test_template')
-rwxr-xr-x | contrib/reghunt/date_based/reg_test_template | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/contrib/reghunt/date_based/reg_test_template b/contrib/reghunt/date_based/reg_test_template new file mode 100755 index 000000000..ab5bbc106 --- /dev/null +++ b/contrib/reghunt/date_based/reg_test_template @@ -0,0 +1,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 |