From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jonathan Tan" <jonathantanmy@google.com>,
"Brandon Williams" <bmwill@google.com>,
"Christian Couder" <chriscool@tuxfamily.org>
Subject: Re: [PATCH 2/3] t: add t0016-oidmap.sh
Date: Sun, 9 Jun 2019 11:22:59 +0200 [thread overview]
Message-ID: <20190609092259.GB24208@szeder.dev> (raw)
In-Reply-To: <20190609044907.32477-3-chriscool@tuxfamily.org>
On Sun, Jun 09, 2019 at 06:49:06AM +0200, Christian Couder wrote:
> From: Christian Couder <christian.couder@gmail.com>
>
> Add actual tests for operations using `struct oidmap` from oidmap.{c,h}.
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> t/t0016-oidmap.sh | 100 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 100 insertions(+)
> create mode 100755 t/t0016-oidmap.sh
>
> diff --git a/t/t0016-oidmap.sh b/t/t0016-oidmap.sh
> new file mode 100755
> index 0000000000..3a8e8bdb3d
> --- /dev/null
> +++ b/t/t0016-oidmap.sh
> @@ -0,0 +1,100 @@
> +#!/bin/sh
> +
> +test_description='test oidmap'
> +. ./test-lib.sh
> +
> +# This purposefully is very similar to t0011-hashmap.sh
> +
> +test_oidmap() {
> + echo "$1" | test-tool oidmap $3 > actual &&
> + echo "$2" > expect &&
Style nit: space between redirection op and filename.
> + test_cmp expect actual
> +}
> +
> +
> +test_expect_success 'setup' '
> +
> + test_commit one &&
> + test_commit two &&
> + test_commit three &&
> + test_commit four
> +
> +'
> +
> +test_oidhash() {
> + git rev-parse "$1" | perl -ne 'print hex("$4$3$2$1") . "\n" if m/^(..)(..)(..)(..).*/;'
New Perl dependencies always make Dscho sad... :)
So, 'test oidmap' from the previous patch prints the value we want to
check with:
printf("%u\n", sha1hash(oid.hash));
First, since object ids inherently make more sense as hex values, it
would be more appropriate to print that hash with the '%x' format
specifier, and then we wouldn't need Perl's hex() anymore, and thus
could swap the order of the first four bytes in oidmap's hash without
relying on Perl, e.g. with:
sed -e 's/^\(..\)\(..\)\(..\)\(..\).*/\4\3\2\1/'
Second, and more importantly, the need for swapping the byte order
indicates that this test would fail on big-endian systems, I'm afraid.
So I think we need an additional bswap32() on the printing side, and
then could further simplify 'test_oidhash':
diff --git a/t/helper/test-oidmap.c b/t/helper/test-oidmap.c
index 0ba122a264..4177912f9a 100644
--- a/t/helper/test-oidmap.c
+++ b/t/helper/test-oidmap.c
@@ -51,7 +51,7 @@ int cmd__oidmap(int argc, const char **argv)
/* print hash of oid */
if (!get_oid(p1, &oid))
- printf("%u\n", sha1hash(oid.hash));
+ printf("%x\n", bswap32(sha1hash(oid.hash)));
else
printf("Unknown oid: %s\n", p1);
diff --git a/t/t0016-oidmap.sh b/t/t0016-oidmap.sh
index 3a8e8bdb3d..9c0d88a316 100755
--- a/t/t0016-oidmap.sh
+++ b/t/t0016-oidmap.sh
@@ -22,10 +22,10 @@ test_expect_success 'setup' '
'
test_oidhash() {
- git rev-parse "$1" | perl -ne 'print hex("$4$3$2$1") . "\n" if m/^(..)(..)(..)(..).*/;'
+ git rev-parse "$1" | cut -c1-8
}
-test_expect_success PERL 'hash' '
+test_expect_success 'hash' '
test_oidmap "hash one
hash two
> +}
> +
> +test_expect_success PERL 'hash' '
> +
> +test_oidmap "hash one
> +hash two
> +hash invalidOid
> +hash three" "$(test_oidhash one)
> +$(test_oidhash two)
> +Unknown oid: invalidOid
> +$(test_oidhash three)"
> +
> +'
> +
> +test_expect_success 'put' '
> +
> +test_oidmap "put one 1
> +put two 2
> +put invalidOid 4
> +put three 3" "NULL
> +NULL
> +Unknown oid: invalidOid
> +NULL"
> +
> +'
> +
> +test_expect_success 'replace' '
> +
> +test_oidmap "put one 1
> +put two 2
> +put three 3
> +put invalidOid 4
> +put two deux
> +put one un" "NULL
> +NULL
> +NULL
> +Unknown oid: invalidOid
> +2
> +1"
> +
> +'
> +
> +test_expect_success 'get' '
> +
> +test_oidmap "put one 1
> +put two 2
> +put three 3
> +get two
> +get four
> +get invalidOid
> +get one" "NULL
> +NULL
> +NULL
> +2
> +NULL
> +Unknown oid: invalidOid
> +1"
> +
> +'
> +
> +test_expect_success 'iterate' '
> +
> +test_oidmap "put one 1
> +put two 2
> +put three 3
> +iterate" "NULL
> +NULL
> +NULL
> +$(git rev-parse two) 2
> +$(git rev-parse one) 1
> +$(git rev-parse three) 3"
> +
> +'
> +
> +test_done
> --
> 2.22.0.14.g9023ccb50a
>
next prev parent reply other threads:[~2019-06-09 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 4:49 [PATCH 0/3] Test oidmap Christian Couder
2019-06-09 4:49 ` [PATCH 1/3] t/helper: add test-oidmap.c Christian Couder
2019-06-09 4:49 ` [PATCH 2/3] t: add t0016-oidmap.sh Christian Couder
2019-06-09 9:22 ` SZEDER Gábor [this message]
2019-06-09 20:24 ` Christian Couder
2019-06-09 21:21 ` SZEDER Gábor
2019-06-09 21:51 ` Christian Couder
2019-06-10 16:46 ` Junio C Hamano
2019-06-13 17:19 ` Jeff King
2019-06-13 17:52 ` SZEDER Gábor
2019-06-13 19:02 ` Jeff King
2019-06-13 22:22 ` Junio C Hamano
2019-06-14 10:36 ` Christian Couder
2019-06-09 4:49 ` [PATCH 3/3] oidmap: use sha1hash() instead of static hash() function Christian Couder
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=20190609092259.GB24208@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.