not ok 65 - describe works in a deep repo # # git tag -f far-far-away HEAD~7999 && # echo "far-far-away" >expect && # git describe --tags --abbrev=0 HEAD~4000 >actual && # test_cmp expect actual && # run_with_limited_stack git describe --tags --abbrev=0 HEAD~4000 >actual && # test_cmp expect actual # not ok 185 - --contains and --no-contains work in a deep repo # # >expect && # i=1 && # while test $i -lt 8000 # do # echo "commit refs/heads/master # committer A U Thor <author@example.com> $((1000000000 + $i * 100)) +0200 # data <<EOF # commit #$i # EOF" # test $i = 1 && echo "from refs/heads/master^0" # i=$(($i + 1)) # done | git fast-import && # git checkout master && # git tag far-far-away HEAD^ && # run_with_limited_stack git tag --contains HEAD >actual && # test_cmp expect actual && # run_with_limited_stack git tag --no-contains HEAD >actual && # test_line_count "-gt" 10 actual # failed test(s): t6120 t7004 fixed 0 success 16540 failed 2 broken 219 total 16987 Both tests write something with "limited_stack", so I _suspect_ that this could go wrong because the stack grows upwards on HPPA.
Created attachment 534366 [details] build.log
(In reply to Rolf Eike Beer from comment #0) > Both tests write something with "limited_stack", so I _suspect_ that this > could go wrong because the stack grows upwards on HPPA. I think it's more likely that it just runs out of stack space. We've had prior issues with the limited stack space that were not resolved because there was a downside to increasing it.
Still happens with 2.20.1 and 2.21.0.
(In reply to Rolf Eike Beer from comment #0) > Both tests write something with "limited_stack", so I _suspect_ that this > could go wrong because the stack grows upwards on HPPA. I wouldn't think git is concerned with stack direction, but more likely with the actual stack limit. We've previously seen problems with programs hitting the stack limit on HPPA.
Still happens in 2.23.0
Still in 2.26.3.
2.33.1 has more failures: failed test(s): t3425 t4014 t7512 t7600 t7610 t7810 fixed 0 success 22808 failed 19 broken 218 total 23430
2.34.1 is down to one error: 7810 not ok 183 - grep --perl-regexp pattern # # git grep --perl-regexp "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # ok 184 # skip grep --perl-regexp pattern errors without PCRE (missing !PCRE of !FAIL_PREREQS,!PCRE) not ok 185 - grep -P pattern # # git grep -P "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # not ok 186 - grep -P with (*NO_JIT) doesn't error out # # git grep -P "(*NO_JIT)\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # # ok 187 # skip grep -P pattern errors without PCRE (missing !PCRE of !FAIL_PREREQS,!PCRE) ok 188 - grep pattern with grep.extendedRegexp=true not ok 189 - grep -P pattern with grep.extendedRegexp=true # # git -c grep.extendedregexp=true \ # grep -P "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual #
Looks gone for me on dev-vcs/git-2.38.2. Retest please? missing prereq: !PCRE !PTHREADS !REFFILES AUTOIDENT CASE_INSENSITIVE_FS EXPENSIVE FSMONITOR_DAEMON GETTEXT_ISO_LOCALE GETTEXT_LOCALE GPG GPGSM GPGSSH_VERIFYTIME JGIT LONG_IS_64BIT MINGW NATIVE_CRLF PERLJSON REGEX_LOCALE RFC1991 RUNTIME_PREFIX SETFACL SIZE_T_IS_64BIT SYMLINKS_WINDOWS TAR_HUGE TAR_NEEDS_PAX_FALLBACK TIME_T_IS_64BIT TTY ULIMIT_STACK_SIZE USR_BIN_TIME UTF8_NFD_TO_NFC WINDOWS fixed 0 success 24540 failed 0 broken 209 total 25309
missing prereq: !PCRE !PTHREADS !REFFILES AUTOIDENT CASE_INSENSITIVE_FS EXPENSIVE FSMONITOR_DAEMON GETTEXT_ISO_LOCALE GETTEXT_LOCALE GPG GPGSM JGIT LONG_IS_64BIT MINGW NATIVE_CRLF PERLJSON REGEX_LOCALE RFC1991 RUNTIME_PREFIX SETFACL SIZE_T_IS_64BIT SYMLINKS_WINDOWS TAR_HUGE TAR_NEEDS_PAX_FALLBACK TIME_T_IS_64BIT TTY ULIMIT_STACK_SIZE USR_BIN_TIME UTF8_NFD_TO_NFC WINDOWS failed test(s): t7810 fixed 0 success 24714 failed 4 broken 209 total 25467 * ERROR: dev-vcs/git-2.38.2::gentoo failed (test phase):
not ok 210 - grep --perl-regexp pattern # # git grep --perl-regexp "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # ok 211 # skip grep --perl-regexp pattern errors without PCRE (missing !PCRE of !FAIL_PREREQS,!PCRE) not ok 212 - grep -P pattern # # git grep -P "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # *** t7814-grep-recurse-submodules.sh *** not ok 213 - grep -P with (*NO_JIT) doesn't error out # # git grep -P "(*NO_JIT)\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual # # ok 214 # skip grep -P pattern errors without PCRE (missing !PCRE of !FAIL_PREREQS,!PCRE) ok 215 - grep pattern with grep.extendedRegexp=true not ok 216 - grep -P pattern with grep.extendedRegexp=true # # git -c grep.extendedregexp=true \ # grep -P "\p{Ps}.*?\p{Pe}" hello.c >actual && # test_cmp expected actual #
Created attachment 845303 [details] build.log for 2.38.2