From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
I'm preparing a series of patches that adjust the test suite so that it
passes on Windows (MinGW port). This is the initial part of it. Another
dozen or more are to follow. By splitting the series I hope to get
earlier feedback.
The series is also available from
git://repo.or.cz/git/mingw/j6t.git for-junio
http://repo.or.cz/w/git/mingw/j6t.git?a=shortlog;h=refs/heads/for-junio
-- Hannes
Johannes Schindelin (1):
t7300: fix clean up on Windows
Johannes Sixt (9):
t9400, t9401: Do not force hard-linked clone
test suite: Use 'say' to say something instead of
'test_expect_success'
Call 'say' outside test_expect_success
test-lib: Replace uses of $(expr ...) by POSIX shell features.
test-lib: Simplify test counting.
test-lib: Introduce test_chmod and use it instead of update-index
--chmod
t2200, t7004: Avoid glob pattern that also matches files
t5300, t5302, t5303: Do not use /dev/zero
t5602: Work around path mangling on MSYS
t/lib-git-svn.sh | 6 +++---
t/t0024-crlf-archive.sh | 2 +-
t/t0050-filesystem.sh | 9 +++++++--
t/t1410-reflog.sh | 4 +---
t/t2200-add-update.sh | 2 +-
t/t3400-rebase.sh | 4 ++--
t/t3600-rm.sh | 5 +++--
t/t4006-diff-mode.sh | 19 ++++---------------
t/t4013-diff-various.sh | 2 +-
t/t4014-format-patch.sh | 4 +---
t/t5000-tar-tree.sh | 2 +-
t/t5300-pack-object.sh | 17 ++++++++---------
t/t5302-pack-index.sh | 2 +-
t/t5303-pack-corruption-resilience.sh | 12 +++++++-----
t/t5515-fetch-merge-logic.sh | 2 +-
t/t5602-clone-remote-exec.sh | 4 ++--
t/t6031-merge-recursive.sh | 9 ++-------
t/t7004-tag.sh | 9 +++++----
t/t7005-editor.sh | 29 +++++++++++++----------------
t/t7300-clean.sh | 6 +++---
t/t9200-git-cvsexportcommit.sh | 2 +-
t/t9400-git-cvsserver-server.sh | 8 ++++----
t/t9401-git-cvsserver-crlf.sh | 6 +++---
t/t9500-gitweb-standalone-no-errors.sh | 20 ++++++--------------
t/t9700-perl-git.sh | 2 +-
t/test-lib.sh | 28 ++++++++++++++++------------
26 files changed, 98 insertions(+), 117 deletions(-)
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
MSYS's bash rewrites /something/bin/... into a Windows path that looks like
c:/msysgit/something/bin/... before git sees it. But later the test case
verifies that the path was used and compares it to the unmangled version.
This fails, of course. This make the path relative so that the path
mangling is not triggered.
Signed-off-by: Johannes Sixt <redacted>
---
t/t5602-clone-remote-exec.sh | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
The tests do not depend on that the clones are hard-linked, but used
--local only as an optimization: At the time that --local was used first
in t9400 hard-linked clones were not the default, yet.
By removing --local, we help filesystems that do not support hard-links.
Signed-off-by: Johannes Sixt <redacted>
---
t/t9400-git-cvsserver-server.sh | 4 ++--
t/t9401-git-cvsserver-crlf.sh | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
Since the test case counter was incremented very late, there were a few
users of the counter had to do their own incrementing. Now we increment it
early and simplify these users.
Signed-off-by: Johannes Sixt <redacted>
---
t/test-lib.sh | 10 +++-------
1 files changed, 3 insertions(+), 7 deletions(-)
@@ -368,7 +364,7 @@ test_external () {then# Announce the script to reduce confusion about the# test output that follows.-say_color""" run $(($test_count+1)): $descr ($*)"+say_color""" run $test_count: $descr ($*)"# Run command; redirect its stderr to &4 as in# test_run_, but keep its stdout on our stdout even in# non-verbose mode.
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
Some tests report that some tests will be skipped. They used
'test_exect_success' with a trivially successful test. Nowadays we have
the helper function 'say' for this purpose.
Signed-off-by: Johannes Sixt <redacted>
---
t/lib-git-svn.sh | 6 +++---
t/t0024-crlf-archive.sh | 2 +-
t/t3600-rm.sh | 2 +-
t/t5000-tar-tree.sh | 2 +-
t/t7004-tag.sh | 4 ++--
t/t9200-git-cvsexportcommit.sh | 2 +-
t/t9400-git-cvsserver-server.sh | 4 ++--
t/t9401-git-cvsserver-crlf.sh | 4 ++--
t/t9500-gitweb-standalone-no-errors.sh | 2 +-
t/t9700-perl-git.sh | 2 +-
10 files changed, 15 insertions(+), 15 deletions(-)
@@ -28,7 +28,7 @@ test_expect_success 'tar archive' '"$UNZIP"-v>/dev/null2>&1if[$?-eq127];then-echo"Skipping ZIP test, because unzip was not found"+say"Skipping ZIP test, because unzip was not found"test_doneexitfi
@@ -182,7 +182,7 @@ test_expect_success 'git archive --format=zip with --output' \$UNZIP-v>/dev/null2>&1if[$?-eq127];then-echo"Skipping ZIP tests, because unzip was not found"+say"Skipping ZIP tests, because unzip was not found"test_doneexitfi
@@ -582,7 +582,7 @@ test_expect_success \# subsequent tests require gpg; check if it is available gpg--version>/dev/nullif[$?-eq127];then-echo"gpg not found - skipping tag signing and verification tests"+say"gpg not found - skipping tag signing and verification tests"test_doneexitfi
@@ -614,7 +614,7 @@ test_expect_success \# that version, creation of signed tags using the generated key fails.case"$(gpg--version)"in'gpg (GnuPG) 1.0.6'*)-echo"Skipping signed tag tests, because a bug in 1.0.6 version"+say"Skipping signed tag tests, because a bug in 1.0.6 version"test_doneexit;;
@@ -74,7 +74,7 @@ safe_chmod () { ../test-lib.sh perl-MEncode-e'decode_utf8("", Encode::FB_CROAK)'>/dev/null2>&1||{-test_expect_success'skipping gitweb tests, perl version is too old':+say'skipping gitweb tests, perl version is too old'test_doneexit}
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
From: Johannes Schindelin <redacted>
On Windows, you cannot remove files that are in use, not even with
'rm -rf'. So we need to run 'exec <foo/bar' inside a subshell lest
removing the whole test repository fail.
Signed-off-by: Johannes Schindelin <redacted>
Signed-off-by: Johannes Sixt <redacted>
---
t/t7300-clean.sh | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
In particular:
- Test case counting can be achieved by arithmetic expansion.
- The name of the test, e.g. t1234, can be computed with ${0%%} and ${0##}.
Signed-off-by: Johannes Sixt <redacted>
---
t/t4013-diff-various.sh | 2 +-
t/t5515-fetch-merge-logic.sh | 2 +-
t/test-lib.sh | 23 +++++++++++------------
3 files changed, 13 insertions(+), 14 deletions(-)
@@ -370,7 +368,7 @@ test_external () {then# Announce the script to reduce confusion about the# test output that follows.-say_color""" run $(expr"$test_count"+1): $descr ($*)"+say_color""" run $(($test_count+1)): $descr ($*)"# Run command; redirect its stderr to &4 as in# test_run_, but keep its stdout on our stdout even in# non-verbose mode.
@@ -613,7 +611,8 @@ test_create_repo "$test"# in subprocesses like git equals our $PWD (for pathname comparisons).cd-P"$test"||exit1-this_test=$(expr"./$0":'.*/\(t[0-9]*\)-[^/]*$')+this_test=${0##*/}+this_test=${this_test%%-*}forskpin$GIT_SKIP_TESTSdoto_skip=
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
We do not have /dev/zero on Windows. This replaces it by data generated
with printf, perl, or echo. Most of the cases do not depend on that the
data is a stream of zero bytes, so we use something printable; nor is an
unlimited stream of data needed, so we produce only as many bytes as the
test cases need.
Signed-off-by: Johannes Sixt <redacted>
---
t/t5300-pack-object.sh | 17 ++++++++---------
t/t5302-pack-index.sh | 2 +-
t/t5303-pack-corruption-resilience.sh | 12 +++++++-----
3 files changed, 16 insertions(+), 15 deletions(-)
@@ -13,11 +13,10 @@ TRASH=`pwd` test_expect_success\'setup'\'rm-f.git/index*-foriinabc-do-ddif=/dev/zerobs=4kcount=1|perl-pe"y/\\000/$i/">$i&&-gitupdate-index--add$i||return1-done&&+perl-e"print \"a\" x 4096;">a&&+perl-e"print \"b\" x 4096;">b&&+perl-e"print \"c\" x 4096;">c&&+gitupdate-index--addabc&&catc>d&&echofoo>>d&&gitupdate-index--addd&&tree=`gitwrite-tree`&&commit=`gitcommit-tree$tree</dev/null`&&{
@@ -66,7 +68,7 @@ test_expect_success \ test_expect_success\'create corruption in header of first object'\-'do_corrupt_object$blob_10</dev/zero&&+'do_corrupt_object$blob_10<zero&&test_must_failgitcat-fileblob$blob_1>/dev/null&&test_must_failgitcat-fileblob$blob_2>/dev/null&&test_must_failgitcat-fileblob$blob_3>/dev/null'
@@ -125,7 +127,7 @@ test_expect_success \'create corruption in header of first delta'\'create_new_pack&&gitprune-packed&&-do_corrupt_object$blob_20</dev/zero&&+do_corrupt_object$blob_20<zero&&gitcat-fileblob$blob_1>/dev/null&&test_must_failgitcat-fileblob$blob_2>/dev/null&&test_must_failgitcat-fileblob$blob_3>/dev/null'
@@ -180,7 +182,7 @@ test_expect_success \'corruption in delta base reference of first delta (OBJ_REF_DELTA)'\'create_new_pack&&gitprune-packed&&-do_corrupt_object$blob_22</dev/zero&&+do_corrupt_object$blob_22<zero&&gitcat-fileblob$blob_1>/dev/null&&test_must_failgitcat-fileblob$blob_2>/dev/null&&test_must_failgitcat-fileblob$blob_3>/dev/null'
@@ -207,7 +209,7 @@ test_expect_success \'corruption #0 in delta base reference of first delta (OBJ_OFS_DELTA)'\'create_new_pack--delta-base-offset&&gitprune-packed&&-do_corrupt_object$blob_22</dev/zero&&+do_corrupt_object$blob_22<zero&&gitcat-fileblob$blob_1>/dev/null&&test_must_failgitcat-fileblob$blob_2>/dev/null&&test_must_failgitcat-fileblob$blob_3>/dev/null'
@@ -259,7 +261,7 @@ test_expect_success \ test_expect_success\'... and a redundant pack allows for full recovery too'\-'do_corrupt_object$blob_22</dev/zero&&+'do_corrupt_object$blob_22<zero&&gitcat-fileblob$blob_1>/dev/null&&test_must_failgitcat-fileblob$blob_2>/dev/null&&test_must_failgitcat-fileblob$blob_3>/dev/null&&
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
This function replaces sequences of 'chmod +x' and 'git update-index
--chmod=+x' in the test suite, whose purpose is to help filesystems
that need core.filemode=false. Two places where only 'chmod +x' was used
we also use this new function.
The function calls 'git update-index --chmod' without checking
core.filemode (unlike some of the call sites did). We do this because the
call sites *expect* that the executable bit ends up in the index (ie. it
is not the purpose of the call sites to *test* whether git treats
'chmod +x' and 'update-index --chmod=+x' correctly). Therefore, on
filesystems with core.filemode=true the 'git update-index --chmod' is a
no-op.
The function uses --add with update-index to help one call site in
t6031-merge-recursive. It makes no difference for the other callers.
Signed-off-by: Johannes Sixt <redacted>
---
t/t1410-reflog.sh | 4 +---
t/t3400-rebase.sh | 4 ++--
t/t4006-diff-mode.sh | 19 ++++---------------
t/t4014-format-patch.sh | 4 +---
t/t6031-merge-recursive.sh | 9 ++-------
t/t9500-gitweb-standalone-no-errors.sh | 18 +++++-------------
t/test-lib.sh | 9 +++++++++
7 files changed, 24 insertions(+), 43 deletions(-)
@@ -15,21 +15,10 @@ test_expect_success \tree=`gitwrite-tree`&&echo$tree'-if["$(gitconfig--getcore.filemode)"=false]-then-say'filemode disabled on the filesystem, using update-index --chmod=+x'-test_expect_success\-'git update-index --chmod=+x'\-'gitupdate-indexrezrov&&-gitupdate-index--chmod=+xrezrov&&-gitdiff-index$tree>current'-else-test_expect_success\-'chmod'\-'chmod+xrezrov&&-gitupdate-indexrezrov&&-gitdiff-index$tree>current'-fi+test_expect_success\+'chmod'\+'test_chmod+xrezrov&&+gitdiff-index$tree>current'_x40='[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]'_x40="$_x40$_x40$_x40$_x40$_x40$_x40$_x40$_x40"
@@ -3,9 +3,6 @@test_description='merge-recursive: handle file mode' ../test-lib.sh-# Note that we follow "chmod +x F" with "update-index --chmod=+x F" to-# help filesystems that do not have the executable bit.- test_expect_success'mode change in one branch: keep changed version'':>file1&&gitaddfile1&&
@@ -15,8 +12,7 @@ test_expect_success 'mode change in one branch: keep changed version' 'gitadddummy&&gitcommit-ma&&gitcheckout-bb1master&&-chmod+xfile1&&-gitupdate-index--chmod=+xfile1&&+test_chmod+xfile1&&gitcommit-mb1&&gitcheckouta1&&gitmerge-recursivemaster--a1b1&&
@@ -28,8 +24,7 @@ test_expect_success 'mode change in both branches: expect conflict' 'gitcheckout-ba2master&&:>file2&&H=$(githash-objectfile2)&&-chmod+xfile2&&-gitupdate-index--add--chmod=+xfile2&&+test_chmod+xfile2&&gitcommit-ma2&&gitcheckout-bb2master&&:>file2&&
@@ -63,14 +63,6 @@ gitweb_run () {# gitweb.log is left for debugging}-safe_chmod(){-chmod"$1""$2"&&-if["$(gitconfig--getcore.filemode)"=false]-then-gitupdate-index--chmod="$1""$2"-fi-}- ../test-lib.sh perl-MEncode-e'decode_utf8("", Encode::FB_CROAK)'>/dev/null2>&1||{
@@ -238,6 +238,15 @@ test_merge () {gittag"$1"}+# This function helps systems where core.filemode=false is set.+# Use it instead of plain 'chmod +x' to set or unset the executable bit+# of a file in the working directory and add it to the index.++test_chmod(){+chmod"$@"&&+gitupdate-index--add"--chmod=$@"+}+# You are not expected to call test_ok_ and test_failure_ directly, use# the text_expect_* functions instead.
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
On Windows, there is an unfortunate interaction between the MSYS bash and
git's command line processing:
- Since Windows's CMD does not do the wildcard expansion, but passes
arguments like path* through to the programs, the programs must do the
expansion themselves. This happens in the startup code before main() is
entered.
- bash, however, passes the argument "path*" to git, assuming that git will
see the unquoted word unchanged as a single argument.
But actually git expands the unquoted word before main() is entered.
In t2200, not all names that the test case is interested in exist as files
at the time when 'git ls-files' is invoked. git expands "path?" to only
the subset of files the exist, and only that subset was listed, so that the
test failed. We now list all interesting paths explicitly.
In t7004, git exanded the pattern "*a*" to "actual" (the file that stdout
was redirected to), which is not what the was tested for. We fix it by
renaming the output file (and removing any existing files matching *a*).
This was originally fixed by Johannes Schindelin.
Signed-off-by: Johannes Sixt <redacted>
---
t/t2200-add-update.sh | 2 +-
t/t7004-tag.sh | 5 +++--
2 files changed, 4 insertions(+), 3 deletions(-)
@@ -185,8 +185,9 @@ cba EOF test_expect_success\'listing tags with substring as pattern must print those matching''-gittag-l"*a*">actual&&-test_cmpexpectactual+rm*a*&&+gittag-l"*a*">current&&+test_cmpexpectcurrent' cat>expect<<EOF
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
There were some uses of 'say' inside test_expect_success. But if the tests
were not run in verbose mode, this message went to /dev/null. Pull them out
of test_expect_success.
Signed-off-by: Johannes Sixt <redacted>
---
t/t0050-filesystem.sh | 9 +++++++--
t/t3600-rm.sh | 3 ++-
t/t7005-editor.sh | 29 +++++++++++++----------------
3 files changed, 22 insertions(+), 19 deletions(-)
@@ -8,6 +8,7 @@ auml=`printf '\xc3\xa4'`aumlcdiar=`printf'\x61\xcc\x88'`case_insensitive=+unibad= test_expect_success'see if we expect ''test_case=test_expect_success
@@ -19,7 +20,6 @@ test_expect_success 'see if we expect ' 'thentest_case=test_expect_failurecase_insensitive=t-say"will test on a case insensitive filesystem"fi&&rm-frjunk&&mkdirjunk&&
@@ -27,13 +27,18 @@ test_expect_success 'see if we expect ' 'case"$(cdjunk&&echo*)"in"$aumlcdiar")test_unicode=test_expect_failure-say"will test on a unicode corrupting filesystem"+unibad=t;;*);;esac&&rm-frjunk'+test"$case_insensitive"&&+say"will test on a case insensitive filesystem"+test"$unibad"&&+say"will test on a unicode corrupting filesystem"+iftest"$case_insensitive"then test_expect_success"detection of case insensitive filesystem during repo init"'
@@ -21,10 +21,11 @@ embedded' embedded'&&gitcommit-m'add files with tabs and newlines'else-say'Your filesystem does not allow tabs in filenames.'test_tabs=nfi"+test"$test_tabs"=n&&say'Your filesystem does not allow tabs in filenames.'+# Later we will try removing an unremovable path to make sure# git rm barfs, but if the test is run as root that cannot be# arranged.
@@ -87,30 +87,27 @@ do'done+if!echo'echo space > "$1"'>"e space.sh"+then+say"Skipping; FS does not support spaces in filenames"+test_done+exit+fi+ test_expect_success'editor with a space''-ifecho"echo space > \"\$1\"">"e space.sh"-then-chmoda+x"e space.sh"&&-GIT_EDITOR="./e\ space.sh"gitcommit--amend&&-testspace="$(gitshow-s--pretty=format:%s)"-else-say"Skipping; FS does not support spaces in filenames"-fi+chmoda+x"e space.sh"&&+GIT_EDITOR="./e\ space.sh"gitcommit--amend&&+testspace="$(gitshow-s--pretty=format:%s)"'unsetGIT_EDITOR test_expect_success'core.editor with a space''-iftest-f"e space.sh"-then-gitconfigcore.editor\"./e\ space.sh\"&&-gitcommit--amend&&-testspace="$(gitshow-s--pretty=format:%s)"-else-say"Skipping; FS does not support spaces in filenames"-fi+gitconfigcore.editor\"./e\ space.sh\"&&+gitcommit--amend&&+testspace="$(gitshow-s--pretty=format:%s)"'
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:46:25
Hi,
On Wed, 18 Mar 2009, Johannes Sixt wrote:
In particular:
- Test case counting can be achieved by arithmetic expansion.
- The name of the test, e.g. t1234, can be computed with ${0%%} and ${0##}.
Signed-off-by: Johannes Sixt <redacted>
I guess this makes the tests less slow on Windows? Do you have numbers?
FWIW I run the tests on Windows with -j10 these days, and they take about
15 minutes on a quad core 3GHz machine (which I may use from time to time;
the machine is not mine, otherwise it would run Linux).
Ciao,
Dscho
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:46:25
Hi,
On Wed, 18 Mar 2009, Johannes Sixt wrote:
Since the test case counter was incremented very late, there were a few
users of the counter had to do their own incrementing. Now we increment it
early and simplify these users.
Signed-off-by: Johannes Sixt <redacted>
---
t/test-lib.sh | 10 +++-------
1 files changed, 3 insertions(+), 7 deletions(-)
Do you not need to adjust t4013 and t5515, too?
Ciao,
Dscho
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
Johannes Schindelin schrieb:
Hi,
On Wed, 18 Mar 2009, Johannes Sixt wrote:
quoted
In particular:
- Test case counting can be achieved by arithmetic expansion.
- The name of the test, e.g. t1234, can be computed with ${0%%} and ${0##}.
Signed-off-by: Johannes Sixt <redacted>
I guess this makes the tests less slow on Windows? Do you have numbers?
Actually, while reading through test-lib.sh I found those expr expressions
quite difficult to understand, and my primary intent was to make the code
more readable. Furthermore, as you can see in the hunk that touches
test_known_broken_{ok,failure}_ that the $(( )) construct is already in
use, so it's also a change to improve consistency.
The shorter runtime (primarily on Windows) is just a nice side effect,
although the gain probably vanishes in the noise.
FWIW I run the tests on Windows with -j10 these days, and they take about
15 minutes on a quad core 3GHz machine (which I may use from time to time;
the machine is not mine, otherwise it would run Linux).
Last time I tried -j<something> it bailed out early. I didn't try again
since then. Sequential tests finish in 30-40 minutes here, but I don't run
SVN tests.
-- Hannes
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
Johannes Schindelin schrieb:
Hi,
On Wed, 18 Mar 2009, Johannes Sixt wrote:
quoted
Since the test case counter was incremented very late, there were a few
users of the counter had to do their own incrementing. Now we increment it
early and simplify these users.
Signed-off-by: Johannes Sixt <redacted>
---
t/test-lib.sh | 10 +++-------
1 files changed, 3 insertions(+), 7 deletions(-)
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
Johannes Schindelin schrieb:
Hi,
On Wed, 18 Mar 2009, Johannes Sixt wrote:
quoted
Some tests report that some tests will be skipped. They used
'test_exect_success' with a trivially successful test. Nowadays we have
s/exect/expect/.
quoted
the helper function 'say' for this purpose.
Signed-off-by: Johannes Sixt <redacted>
I see that you exchanged one "say_color" by "say". What is the
difference?
The color. It's a change towards consistency. I figured that the command
to use by the tests is "say", while "say_color" is an implementation
detail of test-lib.sh.
-- Hannes
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:46:25
Hi,
On Thu, 19 Mar 2009, Johannes Sixt wrote:
Johannes Schindelin schrieb:
quoted
On Wed, 18 Mar 2009, Johannes Sixt wrote:
quoted
In particular:
- Test case counting can be achieved by arithmetic expansion.
- The name of the test, e.g. t1234, can be computed with ${0%%} and
${0##}.
Signed-off-by: Johannes Sixt <redacted>
I guess this makes the tests less slow on Windows? Do you have
numbers?
Actually, while reading through test-lib.sh I found those expr
expressions quite difficult to understand, and my primary intent was to
make the code more readable. Furthermore, as you can see in the hunk
that touches test_known_broken_{ok,failure}_ that the $(( )) construct
is already in use, so it's also a change to improve consistency.
The shorter runtime (primarily on Windows) is just a nice side effect,
although the gain probably vanishes in the noise.
Actually, I should not have written that mail that late at night: 'expr'
is a bash builtin.
quoted
FWIW I run the tests on Windows with -j10 these days, and they take
about 15 minutes on a quad core 3GHz machine (which I may use from
time to time; the machine is not mine, otherwise it would run Linux).
Last time I tried -j<something> it bailed out early. I didn't try again
since then. Sequential tests finish in 30-40 minutes here, but I don't
run SVN tests.
In msysGit, I updated the /share/msysGit/run-tests.sh script to make use
of -j5. If you work on a newer branch than 'devel', you most probably
need the changes from 'release-preview', as my
test-results/<basename>-<pid> patch broke the original assumption of
run-tests.sh.
Ciao,
Dscho
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:46:25
Hi,
On Thu, 19 Mar 2009, Johannes Sixt wrote:
Johannes Schindelin schrieb:
quoted
I see that you exchanged one "say_color" by "say". What is the
difference?
The color. It's a change towards consistency. I figured that the command
to use by the tests is "say", while "say_color" is an implementation
detail of test-lib.sh.
Fair enough. Could you say that in the commit message, too, so that
morons like me do not have to ask? ;-)
Thanks,
Dscho
From: Johannes Sixt <hidden> Date: 2016-06-15 22:46:25
On Mittwoch, 18. März 2009, Johannes Sixt wrote:
I'm preparing a series of patches that adjust the test suite so that it
passes on Windows (MinGW port). This is the initial part of it. Another
dozen or more are to follow. By splitting the series I hope to get
earlier feedback.
The series is also available from
git://repo.or.cz/git/mingw/j6t.git for-junio
http://repo.or.cz/w/git/mingw/j6t.git?a=shortlog;h=refs/heads/for-junio
I've updated the series. Would you please pick up it up from the URL
above?
The changes in particular are:
- [PATCH 02/10] test suite: Use 'say' to say something instead of...
Updated commit message.
- [PATCH 04/10] test-lib: Replace uses of $(expr ...) by POSIX...
No changes to t4013 and t5515 anymore; the next patch removes the
lines that this patch touched.
- [PATCH 05/10] test-lib: Simplify test counting.
Do not use $test_count+1 in t4013 and t5515.
- [PATCH 08/10] t2200, t7004: Avoid glob pattern that also...
Added path2 to the list.
Below is the interdiff.
-- Hannes