tests: drop GIT_*_TIMING_TESTS environment variable support

Two tests (t3302 and t3419) used to have their own environment
variable to trigger expensive tests without enabling expensive
tests in other scripts; a user could set GIT_NOTES_TIMING_TESTS
but not GIT_TEST_LONG and run the whole test suite and trigger
expensive tests only in t3302 but not other tests.  The same for
GIT_PATCHID_TIMING_TESTS in t3419.

While this may have seemed a good flexibility, in reality if you are
concentrating on a single test (e.g. t3302), you can just run that
single test with the GIT_TEST_LONG to trigger expensive tests.  It
does not seem worth forcing other people who may want to come up
with their own expensive tests to invent new environment variables
by keeping this convention.

Drop them.

Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/t/t3302-notes-index-expensive.sh b/t/t3302-notes-index-expensive.sh
index 8d44e04354f05856465904700ff0374dae74ba59..7217c5e222baf0b99b934e36b9418c9d8e13ae9d 100755 (executable)
--- a/t/t3302-notes-index-expensive.sh
+++ b/t/t3302-notes-index-expensive.sh
@@ -7,8 +7,6 @@ test_description='Test commit notes index (expensive!)'
 
 . ./test-lib.sh
 
 
 . ./test-lib.sh
 

-test -n "$GIT_NOTES_TIMING_TESTS" && test_set_prereq EXPENSIVE
-

 create_repo () {
        number_of_commits=$1
        nr=0
 create_repo () {
        number_of_commits=$1
        nr=0

diff --git a/t/t3419-rebase-patch-id.sh b/t/t3419-rebase-patch-id.sh
index 9292b499f39925b6832bccd826fb43a8818f155a..217dd79b2e4b5c02ee27f3b913c37c489ec585f2 100755 (executable)
--- a/t/t3419-rebase-patch-id.sh
+++ b/t/t3419-rebase-patch-id.sh
@@ -4,8 +4,6 @@ test_description='git rebase - test patch id computation'
 
 . ./test-lib.sh
 
 
 . ./test-lib.sh
 

-test -n "$GIT_PATCHID_TIMING_TESTS" && test_set_prereq EXPENSIVE
-

 count () {
        i=0
        while test $i -lt $1
 count () {
        i=0
        while test $i -lt $1