Johannes Schindelin 32ed3314c1 t5351: avoid using test_cmp for binary data
The `test_cmp` function is meant to provide nicer output than `cmp` when
expected and actual output of Git commands disagree. The implicit
assumption is that the output is line-based and human readable.

However, aaf81223f48 (unpack-objects: use stream_loose_object() to
unpack large objects, 2022-06-11) introduced a call that compares the
contents of pack files, which are distinctly not line-based nor human
readable.

This causes problems because on Windows, we hand off to the Bash
function `mingw_test_cmp` that compares the lines while ignoring line
ending differences. And this Bash function spends an insane amount of
cycles trying to read in that binary pack file, so that it is almost
indistinguishable from an infinite loop.

For example, t5351 took 1486 seconds in the CI run at
https://github.com/git/git/runs/7398490747?check_suite_focus=true#step:5:171,
to complete. And yes, that is almost half an hour.

Since Git's tests already use `cmp` consistently when comparing pack
files, let's change this instance to use `cmp` instead of `test_cmp`,
too, and fix that performance problem.

Now t5351 takes all of 22 seconds.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2022-07-29 09:09:07 -07:00
2022-07-27 13:42:09 -07:00
2022-07-18 13:31:55 -07:00
2021-03-13 16:00:09 -08:00
2022-07-10 14:43:34 -07:00
2022-03-29 12:22:02 -07:00
2021-05-07 12:47:41 +09:00
2022-07-11 15:38:51 -07:00
2022-07-11 15:38:51 -07:00
2020-08-10 10:23:57 -07:00
2022-01-07 15:19:34 -08:00
2021-03-13 16:00:09 -08:00
2022-07-14 15:08:29 -07:00
2022-07-14 15:08:29 -07:00
2022-05-10 17:41:10 -07:00
2022-06-10 15:04:13 -07:00
2020-07-06 22:09:13 -07:00
2022-07-19 12:45:31 -07:00
2021-03-13 16:00:09 -08:00
2022-07-18 13:31:57 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2022-06-03 14:30:34 -07:00
2022-03-28 10:25:52 -07:00
2021-09-23 13:44:48 -07:00
2022-06-23 12:36:12 +02:00
2022-07-27 09:16:55 -07:00
2022-07-04 13:45:08 -07:00
2022-07-10 14:43:34 -07:00
2021-03-13 16:00:09 -08:00
2022-06-13 15:53:41 -07:00
2022-07-19 16:40:19 -07:00
2022-04-06 15:21:59 -07:00
2022-05-02 09:50:37 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-05-02 09:50:37 -07:00
2022-07-18 13:31:58 -07:00
2022-01-27 12:07:53 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2022-06-03 14:30:34 -07:00
2022-06-10 15:04:13 -07:00
2021-08-24 15:32:37 -07:00
2020-10-27 15:09:50 -07:00
2022-07-19 16:40:16 -07:00
2022-04-06 09:42:12 -07:00
2022-07-18 13:31:54 -07:00
2022-06-10 15:04:13 -07:00
2022-04-20 16:17:33 -07:00
2022-04-20 16:17:33 -07:00
2022-06-10 15:04:13 -07:00
2022-07-19 12:45:31 -07:00
2022-03-23 14:09:29 -07:00
2021-05-04 11:52:02 +09:00
2021-05-04 11:52:02 +09:00
2022-05-02 09:50:37 -07:00
2022-06-10 15:04:13 -07:00

Build status

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-<commandname>.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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org (not the Git list). The mailing list archives are available at https://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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 612 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%