On 25/09/2026 07:56, Thomas Klausner wrote:
On Fri, Sep 25, 2026 at 01:03:06AM +0100, Pádraig Brady wrote:
On 24/09/2026 22:37, Thomas Klausner wrote:
make TESTS=tests/stat/stat-birthtime.sh SUBDIRS=. check
Fails every time.
Manual test:
# touch a || fail=1
# btime=$(stat --format %W a) || fail=1
# atime=$(stat --format %X a) || fail=1
# ctime=$(stat --format %Z a) || fail=1
# mtime=$(stat --format %Y a) || fail=1
# echo $btime $atime $ctime $mtime
1790285360 1790285360 1790285360 1790285360
(wait a bit)
# touch a || fail=1
# btime=$(stat --format %W a) || fail=1
# atime=$(stat --format %X a) || fail=1
# ctime=$(stat --format %Z a) || fail=1
# mtime=$(stat --format %Y a) || fail=1
# echo $btime $atime $ctime $mtime
1790285360 1790285451 1790285360 1790285451
So ... mtime changed and it should according to the test?
They all should change apart from btime,
ctime is 1790285360 in both cases.
Oh right.
We have seen ctime not being updated when only one of atime or mtime was being
updated,
and have workarounds in gnulib for that. But not when we're updating both, like
a
default touch(1) should do. Does the system touch(1) cause the same issue?
The output from `grep -Fi utime lib/config.h` would be useful also
to determine what gnulib is detecting on your system.
What file system type is this?
Does it happen on other file system types?
thanks,
Padraig
