From: David Turner <dturner@twopensource.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>,
David Turner <dturner@twitter.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH 3/4 v6] cache-tree: subdirectory tests
Date: Fri, 11 Jul 2014 15:46:36 -0700 [thread overview]
Message-ID: <1405118796.3775.27.camel@stross> (raw)
In-Reply-To: <xmqqbnsv6hmc.fsf@gitster.dls.corp.google.com>
On Fri, 2014-07-11 at 08:27 -0700, Junio C Hamano wrote:
> Eric Sunshine <sunshine@sunshineco.com> writes:
>
> > On Thu, Jul 10, 2014 at 8:31 PM, David Turner <dturner@twopensource.com> wrote:
> >> Add tests to confirm that invalidation of subdirectories neither over-
> >> nor under-invalidates.
> >>
> >> Signed-off-by: David Turner <dturner@twitter.com>
> >> ---
> >> t/t0090-cache-tree.sh | 26 +++++++++++++++++++++++---
> >> 1 file changed, 23 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/t/t0090-cache-tree.sh b/t/t0090-cache-tree.sh
> >> index 98fb1ab..3a3342e 100755
> >> --- a/t/t0090-cache-tree.sh
> >> +++ b/t/t0090-cache-tree.sh
> >> @@ -22,9 +22,10 @@ test_shallow_cache_tree () {
> >> }
> >>
> >> test_invalid_cache_tree () {
> >> - echo "invalid (0 subtrees)" >expect &&
> >> - printf "SHA #(ref) (%d entries, 0 subtrees)\n" $(git ls-files|wc -l) >>expect &&
> >> - cmp_cache_tree expect
> >> + printf "invalid %s ()\n" "" "$@" >expect &&
>
> Hmm. This will always expect that the top-level is invalid, even
> when $# is 0. It is OK if you never need to use this to test that a
> cache-tree is fully valid, but is it something we want to check?
We have test_cache_tree to check that it's fully valid.
> Existing tests are mostly about "cache-tree is populated fully at a
> few strategic, well known and easy places and then it degrades over
> time", but after all your series is adding more places to that set
> of "a few places", so we may want to make sure that future breakages
> to the new code paths that "repair" the cache-tree are caught by
> these tests.
This patchset un-failed "initial commit has cache-tree", and added
"commit in child dir has cache-tree" and "partial commit gives
cache-tree". I've just added a test for interactive commit; when you
take a look at the next patchset, you can let me know if this seems
sufficient to you.
next prev parent reply other threads:[~2014-07-11 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 0:31 [PATCH 1/4 v6] cache-tree: Create/update cache-tree on checkout David Turner
2014-07-11 0:31 ` [PATCH 2/4 v6] test-dump-cache-tree: invalid trees are not errors David Turner
2014-07-11 0:31 ` [PATCH 3/4 v6] cache-tree: subdirectory tests David Turner
2014-07-11 6:03 ` Eric Sunshine
2014-07-11 15:27 ` Junio C Hamano
2014-07-11 15:40 ` Junio C Hamano
2014-07-11 22:46 ` David Turner
2014-07-13 16:42 ` Junio C Hamano
2014-07-11 22:46 ` David Turner [this message]
2014-07-11 0:31 ` [PATCH 4/4 v6] cache-tree: Write updated cache-tree after commit David Turner
2014-07-11 15:52 ` Junio C Hamano
2014-07-11 23:37 ` David Turner
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=1405118796.3775.27.camel@stross \
--to=dturner@twopensource.com \
--cc=dturner@twitter.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).