From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] alternate hash test
Date: Sun, 28 Jan 2018 19:32:39 +0100 [thread overview]
Message-ID: <20180128183239.11237-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <20180128170639.216397-1-sandals@crustytoothpaste.net>
> This series wires up an alternate hash implementation, namely
> BLAKE2b-160. The goal is to allow us to identify tests which rely on
> the hash algorithm in use so that we can fix those tests.
> t9903-bash-prompt.sh (Wstat: 256 Tests: 66 Failed: 53)
> Failed tests: 4, 6-10, 14-34, 36, 39-62, 65
> Non-zero exit status: 1
I didn't recall seeing hardcoded SHA-1s in the bash prompt tests, so
went to have a look. And indeed, these failures are not the test's
fault, but the result of a segfault in 'git checkout' while trying to
return from an orphan branch in test 4. The rest of the failures are
mostly fallout caused by the wrong branch being checked out or the
leftover index.lock.
$ ./t9903-bash-prompt.sh -v -i
<...>
expecting success:
printf " (unborn)" >expected &&
git checkout --orphan unborn &&
test_when_finished "git checkout master" &&
__git_ps1 >"$actual" &&
test_cmp expected "$actual"
Switched to a new branch 'unborn'
./test-lib.sh: line 609: 29342 Segmentation fault git checkout master
not ok 4 - prompt - unborn branch
$ gdb --args ../../git checkout master
<...>
Program received signal SIGSEGV, Segmentation fault.
0x000000000041b636 in merge_working_tree (opts=0x7fffffffd200,
old=0x7fffffffd0d0, new=0x7fffffffd1e0,
writeout_error=0x7fffffffd0c0)
at builtin/checkout.c:525
525 init_tree_desc(&trees[0], tree->buffer,
tree->size);
(gdb) p tree
$1 = (struct tree *) 0x0
The root cause is that patch 2/2 misses places where EMPTY_TREE_SHA1_*
constants should have been replaced with their EMPTY_TREE_SBLAKE2B_*
counterparts.
next prev parent reply other threads:[~2018-01-28 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 17:06 [RFC PATCH 0/2] alternate hash test brian m. carlson
2018-01-28 17:06 ` [RFC PATCH 1/2] Base test implementation for short BLAKE2b support brian m. carlson
2018-01-28 17:06 ` [RFC PATCH 2/2] Switch default hash algorithm to short BLAKE2b for testing brian m. carlson
2018-01-28 18:32 ` SZEDER Gábor [this message]
2018-01-28 18:58 ` [RFC PATCH 0/2] alternate hash test Ævar Arnfjörð Bjarmason
2018-01-28 19:16 ` brian m. carlson
2018-01-30 21:09 ` Junio C Hamano
2018-01-31 1:04 ` Stefan Beller
2018-02-01 1:25 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180128183239.11237-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).