| commit | 9b680fbd3b47f39e44fe989971676996d4744ed7 | |
| author | David Turner <dturner@twopensource.com> | |
| Mon, 19 Oct 2015 19:48:15 +0000 (19 15:48 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 20 Oct 2015 01:32:28 +0000 (19 18:32 -0700) | ||
| tree | b8a4157074226bb05faf16ef5cdd3452af5df36f | treesnapshot (tar.gz zip) |
| parent | 73f9145fbf748d39dd1e145ec846a5481cf7a36f | commitdiff |
t7063: fix flaky untracked-cache test
Dirty the test worktree's root directory, as the test expects.
When testing the untracked-cache, we previously assumed that checking
out master would be sufficient to mark the mtime of the worktree's
root directory as racily-dirty. But sometimes, the checkout would
happen at 12345.999 seconds and the status at 12346.001 seconds,
meaning that the worktree's root directory would not be racily-dirty.
And since it was not truly dirty, occasionally the test would fail.
By making the root truly dirty, the test will always succeed.
Tested by running a few hundred times.
Signed-off-by: David Turner <dturner@twopensource.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Dirty the test worktree's root directory, as the test expects.
When testing the untracked-cache, we previously assumed that checking
out master would be sufficient to mark the mtime of the worktree's
root directory as racily-dirty. But sometimes, the checkout would
happen at 12345.999 seconds and the status at 12346.001 seconds,
meaning that the worktree's root directory would not be racily-dirty.
And since it was not truly dirty, occasionally the test would fail.
By making the root truly dirty, the test will always succeed.
Tested by running a few hundred times.
Signed-off-by: David Turner <dturner@twopensource.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t7063-status-untracked-cache.sh | diffblobblamehistory |