On 10/11/19 6:26 PM, Junio C Hamano wrote: > "William Baker via GitGitGadget" <gitgitgad...@gmail.com> writes: > >> +# Test staging/unstaging files that appear at the end of the index. Test >> +# file names begin with 'z' so that they are sorted to the end of the >> index. > > Well, the test is now done in a freshly created repository, so the > z* files are the only thing you have in here---technically they are > at the end of the index, but so they are at the beginning, too. >
There is one other file in the index created by 'test_commit', however, the point still stands that there are almost no other entries in the index now that the test is using its own repository. > Would it affect the effectiveness of the test that you do not have > any other paths in the working tree or in the index, unlike the test > in the previous rounds that did not use a newly created test > repository? The test still validates the scenario that we're concerned about, namely that the new index that's written has less entries than the index of the last entry in the old index that's is not flagged with CE_FSMONITOR_VALID but is flagged for removal (CE_REMOVE). > This is not a rhetorical question, but purely asking. "no, this > still tests what we want to test and shows breakage when the fix to > the code in the patch gets reverted" is perfectly a good answer, but > in that case, is "the end of" the most important trait of the > condition this test is checking? Wouldn't the bug be exposed as > long as we remove sufficiently large number of entries (like > "removing more paths than the paths still in the index at the end" > or something like that)? This is exactly right. The most important trait is that the last entry flagged with CE_REMOVE does not have CE_FSMONITOR_VALID set and has an index >= the number of entries in the new index being written. I will send out a patch on top of 'wb/fsmonitor-bitmap-fix' with an update to the comment for this test. Thanks, William
