summaryrefslogtreecommitdiff
path: root/t/README
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2021-05-20 08:55:00 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-05-20 08:55:00 +0900
commitcb227d5cd65952d11354e008c97e97f4b3e59ca4 (patch)
tree11fc35748f8bd9c9b45c3b04410550a9c46f186d /t/README
parentMerge branch 'en/prompt-under-set-u' (diff)
parentt: avoid sed-based chain-linting in some expensive cases (diff)
downloadtgif-cb227d5cd65952d11354e008c97e97f4b3e59ca4.tar.xz
Merge branch 'jk/test-chainlint-softer'
The "chainlint" feature in the test framework is a handy way to catch common mistakes in writing new tests, but tends to get expensive. An knob to selectively disable it has been introduced to help running tests that the developer has not modified. * jk/test-chainlint-softer: t: avoid sed-based chain-linting in some expensive cases
Diffstat (limited to 't/README')
-rw-r--r--t/README5
1 files changed, 5 insertions, 0 deletions
diff --git a/t/README b/t/README
index a8cfd37387..1a2072b2c8 100644
--- a/t/README
+++ b/t/README
@@ -196,6 +196,11 @@ appropriately before running "make". Short options can be bundled, i.e.
this feature by setting the GIT_TEST_CHAIN_LINT environment
variable to "1" or "0", respectively.
+ A few test scripts disable some of the more advanced
+ chain-linting detection in the name of efficiency. You can
+ override this by setting the GIT_TEST_CHAIN_LINT_HARDER
+ environment variable to "1".
+
--stress::
Run the test script repeatedly in multiple parallel jobs until
one of them fails. Useful for reproducing rare failures in