SZEDER Gábor a5bf824f3b t: prevent '-x' tracing from interfering with test helpers' stderr
Running a test script with '-x' turns on 'set -x' tracing, the output
of which is normally sent to stderr.  This causes a lot of
test failures, because many tests redirect and verify the stderr
of shell functions, most frequently that of 'test_must_fail'.
These issues were worked around somewhat in d88785e424 (test-lib: set
BASH_XTRACEFD automatically, 2016-05-11), so at least we could
reliably run tests with '-x' tracing under a Bash version supporting
BASH_XTRACEFD, i.e. v4.1 and later.

Futhermore, redirecting the stderr of test helper functions like
'test_must_fail' or 'test_expect_code' is the cause of a different
issue as well.  If these functions detect something unexpected, they
will write their error messages intended to the user to thier stderr.
However, if their stderr is redirected in order to save and verify the
stderr of the tested git command invoked in the function, then the
function's error messages will be redirected as well.  Consequently,
those messages won't reach the user, making the test's verbose output
less useful.

This patch makes it safe to redirect and verify the stderr of those
test helper functions which are meant to run the tested command given
as argument, even when running tests with '-x' and /bin/sh.  This is
achieved through a couple of file descriptor redirections:

  - Duplicate stderr of the tested command executed in the test helper
    function from the function's fd 7 (see next point), to ensure that
    the tested command's error messages go to a different fd than the
    '-x' trace of the commands executed in the function or the
    function's error messages.

  - Duplicate the test helper function's fd 7 from the function's
    original stderr, meaning that, after taking a detour through fd 7,
    the error messages of the tested command do end up on the
    function's original stderr.

  - Duplicate stderr of the test helper function from fd 4, i.e. the
    fd connected to the test script's original stderr and the fd used
    for BASH_XTRACEFD.  This ensures that the '-x' trace of the
    commands executed in the function

      - doesn't go to the function's original stderr, so it won't mess
	with callers who want to save and verify the tested command's
	stderr.

      - does go to the same fd independently from the shell running
        the test script, be it /bin/sh, an older Bash without
        BASH_XTRACEFD, or a more recent Bash already supporting
        BASH_XTRACEFD.

    Furthermore, this also makes sure that the function's error
    messages go to this fd 4, meaning that the user will be able to
    see them even if the function's stderr is redirected in the test.

  - Specify the latter two redirections above in the test helper
    function's definition, so they are performed every time the
    function is invoked, without the need to modify the callsites of
    the function.

Perform these redirections in those test helper functions which can be
expected to have their stderr redirected, i.e. in the functions
'test_must_fail', 'test_might_fail', 'test_expect_code', 'test_env',
'nongit', 'test_terminal' and 'perl'.  Note that 'test_might_fail',
'test_env', and 'nongit' are not involved in any test failures when
running tests with '-x' and /bin/sh.

The other test helper functions are left unchanged, because they
either don't run commands specified as their arguments, or redirecting
their stderr wouldn't make sense, or both.

With this change the number of failures when running the test suite
with '-x' tracing and /bin/sh goes down from 340 failed tests in 43
test scripts to 22 failed tests in 6 scripts (or 23 in 7, if the
system (OSX) uses an older Bash version without BASH_XTRACEFD to run
't9903-bash-prompt.sh').

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-02-27 12:43:13 -08:00
2017-11-21 14:07:50 +09:00
2018-02-21 12:45:35 -08:00
2018-01-15 07:47:30 +01:00
2017-07-06 18:14:44 -07:00
2018-02-15 14:55:43 -08:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-03-13 15:28:54 -07:00
2017-11-15 12:14:28 +09:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-08-03 11:08:10 -07:00
2017-05-02 10:46:41 +09:00
2018-02-15 14:55:43 -08:00
2018-02-15 14:55:47 -08:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2017-01-25 14:42:37 -08:00
2018-02-15 14:55:43 -08:00
2018-02-13 13:39:08 -08:00
2018-02-13 13:39:04 -08:00
2018-02-15 14:55:43 -08:00
2017-06-24 14:28:41 -07:00
2018-02-02 11:28:41 -08:00
2018-02-02 11:28:41 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-01-23 13:16:37 -08:00
2018-02-15 14:55:43 -08:00
2018-02-15 14:55:44 -08:00
2017-11-21 14:07:50 +09:00
2018-02-13 13:39:04 -08:00
2017-03-31 08:33:56 -07:00
2018-02-15 15:21:23 -08:00
2017-11-28 13:41:50 +09:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2018-01-24 13:42:23 -08:00
2018-02-13 13:39:11 -08:00
2017-06-24 14:28:41 -07:00
2017-01-30 14:17:00 -08:00
2017-09-06 17:19:54 +09:00
2018-02-15 14:55:40 -08:00
2018-02-13 13:39:03 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-02-02 11:28:41 -08:00
2018-02-13 13:39:11 -08:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2018-01-22 11:32:51 -08:00
2017-10-28 10:18:40 +09:00
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2018-01-16 12:16:54 -08:00
2018-01-16 12:16:54 -08:00
2018-02-15 14:55:47 -08:00
2018-02-15 15:21:23 -08:00
2017-12-08 09:58:51 -08:00
2018-01-22 11:32:51 -08:00
2018-01-22 11:32:51 -08:00
2017-03-31 08:33:56 -07:00
2018-02-15 14:55:43 -08:00
2018-02-13 13:39:03 -08:00
2018-02-15 14:55:47 -08:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2017-08-26 22:55:04 -07:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2017-06-24 14:28:41 -07:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2017-11-06 14:24:27 +09:00

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 581 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%