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

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 expesive tests to invent new environment variables by
keeping this convention.

Drop them.

Signed-off-by: Junio C Hamano <>
 t/ | 2 --
 t/       | 2 --
 2 files changed, 4 deletions(-)

diff --git a/t/ b/t/
index 8d44e04..7217c5e 100755
--- a/t/
+++ b/t/
@@ -7,8 +7,6 @@ test_description='Test commit notes index (expensive!)'
 . ./
-test -n "$GIT_NOTES_TIMING_TESTS" && test_set_prereq EXPENSIVE
 create_repo () {
diff --git a/t/ b/t/
index 9292b49..217dd79 100755
--- a/t/
+++ b/t/
@@ -4,8 +4,6 @@ test_description='git rebase - test patch id computation'
 . ./
-test -n "$GIT_PATCHID_TIMING_TESTS" && test_set_prereq EXPENSIVE
 count () {
        while test $i -lt $1

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to