2013-11-26 05:03:06 +08:00
|
|
|
# Helpers for terminal output tests.
|
2010-10-17 02:36:56 +08:00
|
|
|
|
t/lib-terminal: make TTY a lazy prerequisite
When lib-terminal.sh is sourced by a test script, we
immediately set up the TTY prerequisite. We do so inside a
test_expect_success, because that nicely isolates any
generated output.
However, this early test can interfere with a script that
later wants to skip all tests (e.g., t5541 then goes on to
set up the httpd server, and wants to skip_all if that
fails). TAP output doesn't let us skip everything after we
have already run at least one test.
We could fix this by reordering the inclusion of
lib-terminal.sh in t5541 to go after the httpd setup. That
solves this case, but we might eventually hit a case with
circular dependencies, where either lib-*.sh include might
want to skip_all after the other has run a test. So
instead, let's just remove the ordering constraint entirely
by doing the setup inside a test_lazy_prereq construct,
rather than in a regular test. We never cared about the
test outcome anyway (it was written to always succeed).
Note that in addition to setting up the prerequisite, the
current test also defines test_terminal. Since we can't
affect the environment from a lazy_prereq, we have to hoist
that out. We previously depended on it _not_ being defined
when the TTY prereq isn't set as a way to ensure that tests
properly declare their dependency on TTY. However, we still
cover the case (see the in-code comment for details).
Reported-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-15 05:57:23 +08:00
|
|
|
# Catch tests which should depend on TTY but forgot to. There's no need
|
2015-01-21 17:14:01 +08:00
|
|
|
# to additionally check that the TTY prereq is set here. If the test declared
|
t/lib-terminal: make TTY a lazy prerequisite
When lib-terminal.sh is sourced by a test script, we
immediately set up the TTY prerequisite. We do so inside a
test_expect_success, because that nicely isolates any
generated output.
However, this early test can interfere with a script that
later wants to skip all tests (e.g., t5541 then goes on to
set up the httpd server, and wants to skip_all if that
fails). TAP output doesn't let us skip everything after we
have already run at least one test.
We could fix this by reordering the inclusion of
lib-terminal.sh in t5541 to go after the httpd setup. That
solves this case, but we might eventually hit a case with
circular dependencies, where either lib-*.sh include might
want to skip_all after the other has run a test. So
instead, let's just remove the ordering constraint entirely
by doing the setup inside a test_lazy_prereq construct,
rather than in a regular test. We never cared about the
test outcome anyway (it was written to always succeed).
Note that in addition to setting up the prerequisite, the
current test also defines test_terminal. Since we can't
affect the environment from a lazy_prereq, we have to hoist
that out. We previously depended on it _not_ being defined
when the TTY prereq isn't set as a way to ensure that tests
properly declare their dependency on TTY. However, we still
cover the case (see the in-code comment for details).
Reported-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-15 05:57:23 +08:00
|
|
|
# it and we are running the test, then it must have been set.
|
|
|
|
|
test_terminal () {
|
|
|
|
|
if ! test_declared_prereq TTY
|
|
|
|
|
then
|
|
|
|
|
echo >&4 "test_terminal: need to declare TTY prerequisite"
|
|
|
|
|
return 127
|
|
|
|
|
fi
|
|
|
|
|
perl "$TEST_DIRECTORY"/test-terminal.perl "$@"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
test_lazy_prereq TTY '
|
|
|
|
|
test_have_prereq PERL &&
|
|
|
|
|
|
2011-02-17 20:38:52 +08:00
|
|
|
# Reading from the pty master seems to get stuck _sometimes_
|
|
|
|
|
# on Mac OS X 10.5.0, using Perl 5.10.0 or 5.8.9.
|
|
|
|
|
#
|
|
|
|
|
# Reproduction recipe: run
|
|
|
|
|
#
|
|
|
|
|
# i=0
|
|
|
|
|
# while ./test-terminal.perl echo hi $i
|
|
|
|
|
# do
|
|
|
|
|
# : $((i = $i + 1))
|
|
|
|
|
# done
|
|
|
|
|
#
|
|
|
|
|
# After 2000 iterations or so it hangs.
|
|
|
|
|
# https://rt.cpan.org/Ticket/Display.html?id=65692
|
|
|
|
|
#
|
t/lib-terminal: make TTY a lazy prerequisite
When lib-terminal.sh is sourced by a test script, we
immediately set up the TTY prerequisite. We do so inside a
test_expect_success, because that nicely isolates any
generated output.
However, this early test can interfere with a script that
later wants to skip all tests (e.g., t5541 then goes on to
set up the httpd server, and wants to skip_all if that
fails). TAP output doesn't let us skip everything after we
have already run at least one test.
We could fix this by reordering the inclusion of
lib-terminal.sh in t5541 to go after the httpd setup. That
solves this case, but we might eventually hit a case with
circular dependencies, where either lib-*.sh include might
want to skip_all after the other has run a test. So
instead, let's just remove the ordering constraint entirely
by doing the setup inside a test_lazy_prereq construct,
rather than in a regular test. We never cared about the
test outcome anyway (it was written to always succeed).
Note that in addition to setting up the prerequisite, the
current test also defines test_terminal. Since we can't
affect the environment from a lazy_prereq, we have to hoist
that out. We previously depended on it _not_ being defined
when the TTY prereq isn't set as a way to ensure that tests
properly declare their dependency on TTY. However, we still
cover the case (see the in-code comment for details).
Reported-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-15 05:57:23 +08:00
|
|
|
test "$(uname -s)" != Darwin &&
|
|
|
|
|
|
|
|
|
|
perl "$TEST_DIRECTORY"/test-terminal.perl \
|
|
|
|
|
sh -c "test -t 1 && test -t 2"
|
2010-10-17 02:36:56 +08:00
|
|
|
'
|
