| commit | f80d1f95f0adf9909f42eb9e74546963daa4b0c1 | |
| author | Jeff King <peff@peff.net> | |
| Tue, 1 Apr 2014 07:43:06 +0000 (1 03:43 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 1 Apr 2014 21:40:05 +0000 (1 14:40 -0700) | ||
| tree | 075c755aec4819bc9a36adeb4174c229beaa7eb7 | treesnapshot (tar.gz zip) |
| parent | 6654754779d2a90af91a9c6b93d7e4e7ee16cfab | commitdiff |
t4212: loosen far-in-future test for AIX
One of the tests in t4212 checks our behavior when we feed
gmtime a date so far in the future that it gives up and
returns NULL. Some implementations, like AIX, may actually
just provide us a bogus result instead.
It's not worth it for us to come up with heuristics that
guess whether the return value is sensible or not. On good
platforms where gmtime reports the problem to us with NULL,
we will print the epoch value. On bad platforms, we will
print garbage. But our test should be written for the
lowest common denominator so that it passes everywhere.
Reported-by: Charles Bailey <cbailey32@bloomberg.net>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
One of the tests in t4212 checks our behavior when we feed
gmtime a date so far in the future that it gives up and
returns NULL. Some implementations, like AIX, may actually
just provide us a bogus result instead.
It's not worth it for us to come up with heuristics that
guess whether the return value is sensible or not. On good
platforms where gmtime reports the problem to us with NULL,
we will print the epoch value. On bad platforms, we will
print garbage. But our test should be written for the
lowest common denominator so that it passes everywhere.
Reported-by: Charles Bailey <cbailey32@bloomberg.net>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t4212-log-corrupt.sh | diffblobblamehistory |