Junio C Hamano <gits...@pobox.com> writes:
>>> + sed -n -e "s/[0-9]* subtrees//" -e '/#(ref)/d' -e '/^invalid /p'
>>> >actual &&
> Is the second one to remove "#(ref)", which appears for a good
> "reference" cache tree entry shown for comparison, necessary? Do
> they ever begin with "invalid"? If they ever begin with "invalid"
> that itself may even be a noteworthy breakage to catch, no?
Answering to myself...
Because test-dump-cache-tree uses DRY_RUN to create only an in-core
copy of tree object, and we notice that the reference cache-tree
created in the tests contains the object name of a tree that does
not yet exist in the object database. We get "invalid #(ref)" for
In the ideal world, I think whoever tries to compare two cache-trees
(i.e. test-dump-cache-tree) should *not* care, because we are merely
trying to show what the correct tree object name for the node would
be, but this is only for testing, so the best way forward would be
- Stop using DRY_RUN in test-dump-cache-tree.c;
- Stop the code to support DRY_RUN from cache-tree.c (nobody but
the test uses it); and
- Drop the "-e '#(ref)/d'" from the above.
I would think.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html