Mercurial > hg-stable
view tests/helpers-testrepo.sh @ 30237:94ef2f00b8a4 stable
tests: use basic format code "%Y" instead of "%s" for test portability
On Windows, strftime() doesn't support format code "%s", and it causes
"invalid format string" error.
https://msdn.microsoft.com/en-us/library/fe06s4ak.aspx
test-command-template.t examines not seconds value in UTC, but
arithmetic calculation. Therefore, using format code "%Y" instead of
"%s" should be reasonable.
FYI:
- Python standard library reference doesn't list "%s" up in format
code list required for "C standard (1989 version)", even though it
also mentions that additional format codes are required for "C
standard (1999 version)"
https://docs.python.org/2.7/library/datetime.html#strftime-and-strptime-behavior
- The Open Group Base Specifications Issue 7 (IEEE Std 1003.1-2008,
2016 Edition) doesn't require strftime to support format code "%s"
http://pubs.opengroup.org/onlinepubs/9699919799/functions/strftime.html
- "man strftime" of (Open/Oracle) Solaris and Mac OS X (= UNIX
certified OSs) describes about format code "%s"
author | FUJIWARA Katsunori <foozy@lares.dti.ne.jp> |
---|---|
date | Sun, 30 Oct 2016 06:15:07 +0900 |
parents | 3c9066ed557c |
children | 6c113a7dec52 |
line wrap: on
line source
# The test-repo is a live hg repository which may have evolution # markers created, e.g. when a ~/.hgrc enabled evolution. # # Tests are run using a custom HGRCPATH, which do not # enable evolution markers by default. # # If test-repo includes evolution markers, and we do not # enable evolution markers, hg will occasionally complain # when it notices them, which disrupts tests resulting in # sporadic failures. # # Since we aren't performing any write operations on the # test-repo, there's no harm in telling hg that we support # evolution markers, which is what the following lines # for the hgrc file do: cat >> $HGRCPATH << EOF [experimental] evolution=createmarkers EOF