|
From: | Bruce Dubbs |
Subject: | bug#12206: test-parse-datetime regression test failure with glibc-2.16.0 |
Date: | Fri, 17 Aug 2012 12:46:35 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120628 Firefox/13.0.1 SeaMonkey/2.10.1 |
Paul Eggert wrote:
On 08/16/2012 10:30 PM, Bruce Dubbs wrote:When we run the tests, we can change our procedures to set any TZ needed.Could you please try it with TZ='EST5EDT,M3.2.0,M11.1.0'? If that works, we can change the test program to use that TZ value by default.
I found two issues. cd gnulib-tests make check TESTS=test-parse-datetime VERBOSE=yes fails rm /etc/localtime (I have this normally set to GMT for testing) make check TESTS=test-parse-datetime VERBOSE=yes passes restoring /etc/localtime export TZ='EST5EDT,M3.2.0,M11.1.0' make check TESTS=test-parse-datetime VERBOSE=yes passes.We can work with this, but you may want to adjust test-parse-datetime to make it more robust.
Setting TZ to GMT, America/Chicago, or EST5EDT fails Setting TX to UCT0 passes. BTW, I've never seen the M parameters in TZ before. What do they do? -- Bruce
[Prev in Thread] | Current Thread | [Next in Thread] |