summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/1.6.6.3.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2021-01-28 01:32:35 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-01-28 12:06:26 -0800
commit080e29524806484fbf8ee171a222fbcc45a47e43 (patch)
treea471226c505380fff57c4f201d05eb336c4039be /Documentation/RelNotes/1.6.6.3.txt
parentt0000: run prereq tests inside sub-test (diff)
downloadtgif-080e29524806484fbf8ee171a222fbcc45a47e43.tar.xz
t0000: run cleaning test inside sub-test
Our check of test_when_finished is done directly in the main script, and if we failed to clean, we complain and exit immediately. It's nicer to signal a test failure here, for a few reasons: - this gives better output to the user when run under a TAP harness like "prove" - constency; it's the only test left in the file that behaves this way - half of its "if" conditional is nonsense anyway; it picked up a reference to GIT_TEST_FAIL_PREREQS_INTERNAL in dfe1a17df9 (tests: add a special setup where prerequisites fail, 2019-05-13) along with its neighbors, even though it has nothing to do with that flag We could actually do this without a sub-test at all, and just put our two tests (one to do cleanup, and one to check that it happened) in the main script. But doing it in a subtest is conceptually cleaner (from the perspective of the main test script, we are checking only one thing), and it remains consistent with the "cleanup when failing" test directly after it, which has to happen in a sub-test (to avoid the main script complaining of the failed test). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.6.6.3.txt')
0 files changed, 0 insertions, 0 deletions