summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2005-08-13 13:07:45 +0000
committerJim Meyering <jim@meyering.net>2005-08-13 13:07:45 +0000
commit829444c02d2f4e0db913d9b254a091705bfa2a75 (patch)
tree5b47e6d6b14d73e1bf41ba5fb7f935ac9de876c6
parent9d8e8ad5212b2430f17b7ecb49eff46690fb6aec (diff)
downloadcoreutils-829444c02d2f4e0db913d9b254a091705bfa2a75.tar.xz
(test_vector) [cross-dst]: New test for just-fixed getdate.y bug.
-rw-r--r--tests/date/Test.pm9
1 files changed, 9 insertions, 0 deletions
diff --git a/tests/date/Test.pm b/tests/date/Test.pm
index dd6509418..7f6577f08 100644
--- a/tests/date/Test.pm
+++ b/tests/date/Test.pm
@@ -160,6 +160,14 @@ sub test_vector
['empty-fmt', '+', {}, '', 0],
+ # Since coreutils/lib/getdate.y revision 1.96 (post-coreutils-5.3.0),
+ # a command like the following would mistakenly exit nonzero with an
+ # `invalid date ...' diagnostic, but only when run in a time zone for
+ # which that 24-hour range spans a daylight savings time transition.
+ # Unfortunately (for ease of testing), if you set TZ at all, this
+ # failure is not triggered, hence the cross-dst env setting below.
+ ['cross-dst', "--date '2005-03-27 +1 day' +%Y", {}, '2005', 0],
+
# FIXME: add a lot more...
);
@@ -189,6 +197,7 @@ sub test_vector
$Test::env{'rfc822-1'} = ['LC_ALL=de_DE TZ=UTC0'];
$Test::env{'relative-2'} = ['TZ=UTC+1'];
+ $Test::env{'cross-dst'} = ['no_TZ=1'];
return @tv;
}