The test "validate file modification time" was broken on admittedly broken combination of Windows, Cygwin, and ActiveState Perl. Something (I blame ActiveState) of the three is very confused about what time zone to use for the modification time. Signed-off-by: Alex Riesen --- I could not find what exactly does the ActiveState's Perl use for its stat implementation (and honestly, have no motivation to look harder). It seems to honor TZ, but the produced time does not seem to be either local or GMT. There can be a problem with "-printf": Open Group SUS does not specify -printf for find(1), so it is probably a problem somewhere. I just don't know. There is always a fallback, which is to write a small program which calls native stat(2). Or modify test-chmtime to just print mtime when asked. t/t5000-tar-tree.sh | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-)