summaryrefslogtreecommitdiff
path: root/%25253fid%25253d93767ce29c6ea41c40808276aa0ae9fc60d5eca5%253fid%253de27cf190d...
diff options
context:
space:
mode:
authorLukas Fleischer <calcurse@cryptocrack.de>2012-12-22 00:49:29 +0100
committerLukas Fleischer <calcurse@cryptocrack.de>2012-12-22 01:09:17 +0100
commit2ea91e1a8a2ee4318e3530ec2680565ad11b1585 (patch)
tree3ce57c3d13289ba7bc84efa1f79973beded78aa5 /%25253fid%25253d93767ce29c6ea41c40808276aa0ae9fc60d5eca5%253fid%253de27cf190d05e6b07cba1dfe47dd2426a3c167056%3fid%3d217e66729a249a638863a9cc2ff93b8368cd6094?id=2ea91e1a8a2ee4318e3530ec2680565ad11b1585
parentc054182890b5a2145d457d8ecade200d851e95fd (diff)
test/: Use `faketime -f`
Use the advanced timestamp specification format for libfaketime. Before using that, some tests failed on 32-bit systems due to integer overflows. It seems like faketime translates absolute dates to relative dates by default. Moreover, libfaketime is not able to handle relative dates that exceed the maximum value of a signed integer. Using "-f" skips the conversion to relative dates. Signed-off-by: Lukas Fleischer <calcurse@cryptocrack.de>
Diffstat (limited to '%25253fid%25253d93767ce29c6ea41c40808276aa0ae9fc60d5eca5%253fid%253de27cf190d05e6b07cba1dfe47dd2426a3c167056%3fid%3d217e66729a249a638863a9cc2ff93b8368cd6094?id=2ea91e1a8a2ee4318e3530ec2680565ad11b1585')
0 files changed, 0 insertions, 0 deletions