author | Junio C Hamano <gitster@pobox.com> | |
Wed, 7 Apr 2010 00:08:54 +0000 (17:08 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 7 Apr 2010 04:55:27 +0000 (21:55 -0700) | ||
commit | 016e5ff24345f974a084375da83ee143b5f2772d | |
tree | 3bff8253c1825ee04c65a98bc633dee4dfc60423 | tree | snapshot |
parent | 537f6c7fb40257776a513128043112ea43b5cdb8 | commit | diff |
war on "sleep" in tests
In many places in test suite we have "sleep"s that do not have to be
there.
- I do not simply see the point of the one in t3500. It may be making
sure that the timestamp order of commits generated during the test is
stable, in which case test_tick is the right ingredient to use without
wasting tester's time.
- The one in t4011 is to make sure that the plumbing diff-index notices
the stat-dirtyness of a removed then identically recreated symlink.
Keeping the old symlink around to make sure that a newly created
symlink gets different ino would be sufficient for that purpose.
- The one in t7600 is to make sure that "git merge" does not get confused
by stat-dirty "file" in the working tree. Again, keeping the old file
around and creating an identical copy to ensure a different ino would
be sufficient for that purpose.
The "racy git" tests in t0010 are inherently about mtime between the index
itself and index entries. The "sleep" in that test must stay as they are.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In many places in test suite we have "sleep"s that do not have to be
there.
- I do not simply see the point of the one in t3500. It may be making
sure that the timestamp order of commits generated during the test is
stable, in which case test_tick is the right ingredient to use without
wasting tester's time.
- The one in t4011 is to make sure that the plumbing diff-index notices
the stat-dirtyness of a removed then identically recreated symlink.
Keeping the old symlink around to make sure that a newly created
symlink gets different ino would be sufficient for that purpose.
- The one in t7600 is to make sure that "git merge" does not get confused
by stat-dirty "file" in the working tree. Again, keeping the old file
around and creating an identical copy to ensure a different ino would
be sufficient for that purpose.
The "racy git" tests in t0010 are inherently about mtime between the index
itself and index entries. The "sleep" in that test must stay as they are.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t3500-cherry.sh | diff | blob | history | |
t/t4011-diff-symlink.sh | diff | blob | history | |
t/t7600-merge.sh | diff | blob | history |