From: Eric Sunshine <sunshine@sunshineco.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v9 5/5] t1006: add tests for git cat-file --allow-unkown-type
Date: Wed, 29 Apr 2015 17:16:11 -0400 [thread overview]
Message-ID: <CAPig+cSXB1fyRGTtuOGsxiBnAhVwS2DydLmVYmq-+47EAa-7-g@mail.gmail.com> (raw)
In-Reply-To: <1430312065-23443-1-git-send-email-karthik.188@gmail.com>
On Wed, Apr 29, 2015 at 8:54 AM, Karthik Nayak <karthik.188@gmail.com> wrote:
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---
> diff --git a/t/t1006-cat-file.sh b/t/t1006-cat-file.sh
> index ab36b1e..8362019 100755
> --- a/t/t1006-cat-file.sh
> +++ b/t/t1006-cat-file.sh
> @@ -47,6 +47,18 @@ $content"
> test_cmp expect actual
> '
>
> + test_expect_success "Type of $type is correct using --allow-unkown-type" '
> + echo $type >expect &&
> + git cat-file -t --allow-unkown-type $sha1 >actual &&
Somehow the indentation got botched here and in the remaining tests
you added. This issue is new since v8.
> + test_cmp expect actual
> + '
> +
> + test_expect_success "Size of $type is correct using --allow-unkown-type" '
> + echo $size >expect &&
> + git cat-file -s --allow-unkown-type $sha1 >actual &&
> + test_cmp expect actual
> + '
> +
> test -z "$content" ||
> test_expect_success "Content of $type is correct" '
> maybe_remove_timestamp "$content" $no_ts >expect &&
> @@ -296,4 +308,21 @@ test_expect_success '%(deltabase) reports packed delta bases' '
> }
> '
>
> +bogus_type="bogus"
> +bogus_content="bogus"
> +bogus_size=$(strlen "$bogus_content")
> +bogus_sha1=$(echo_without_newline "$bogus_content" | git hash-object -t $bogus_type --literally -w --stdin)
> +
> +test_expect_success "Type of broken object is correct" '
> + echo $bogus_type >expect &&
> + git cat-file -t --allow-unkown-type $bogus_sha1 >actual &&
> + test_cmp expect actual
> +'
> +
> +test_expect_success "Size of broken object is correct" '
> + echo $bogus_size >expect &&
> + git cat-file -s --allow-unkown-type $bogus_sha1 >actual &&
> + test_cmp expect actual
> +'
> +
> test_done
> --
> 2.4.0.rc1.250.g565e85b
next prev parent reply other threads:[~2015-04-29 21:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 12:50 [PATCH v9 0/5] cat-file: teach cat-file a '--allow-unkown-type' option karthik nayak
2015-04-29 12:52 ` [PATCH v9 1/5] sha1_file: support reading from a loose object of unknown type Karthik Nayak
2015-04-29 14:49 ` Junio C Hamano
2015-04-29 17:50 ` karthik nayak
2015-04-29 19:35 ` Junio C Hamano
2015-04-30 4:40 ` karthik nayak
2015-04-29 12:52 ` [PATCH v9 2/5] cat-file: make the options mutually exclusive Karthik Nayak
2015-04-29 12:53 ` [PATCH v9 3/5] cat-file: teach cat-file a '--allow-unknown-type' option Karthik Nayak
2015-04-29 14:52 ` Junio C Hamano
2015-04-29 17:43 ` karthik nayak
2015-04-29 14:53 ` Phil Hord
2015-04-29 17:44 ` karthik nayak
2015-04-29 19:38 ` Junio C Hamano
2015-04-29 12:54 ` [PATCH v9 5/5] t1006: add tests for git cat-file --allow-unkown-type Karthik Nayak
2015-04-29 21:16 ` Eric Sunshine [this message]
2015-04-29 12:56 ` [PATCH v9 4/5] cat-file: add documentation for '--allow-unkown-type' option Karthik Nayak
2015-04-29 21:13 ` Eric Sunshine
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=CAPig+cSXB1fyRGTtuOGsxiBnAhVwS2DydLmVYmq-+47EAa-7-g@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.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 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).