New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

t/doit.t: utime-related tests fail on some NetBSD systems #1

Open
eserte opened this Issue Dec 7, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@eserte
Owner

eserte commented Dec 7, 2017

Sample fail report: http://www.cpantesters.org/cpan/report/e67b15ac-dad1-11e7-b8bd-809199b835e7

It seems that utime() may change mtime, but not atime. Or atime is immediately refresh to "now".

@eserte

This comment has been minimized.

Show comment
Hide comment
@eserte

eserte Dec 7, 2017

Owner

A related issue: golang/go#19293

If the analysis there is right, then atime isn't changed by utime() calls if the filesystem is mounted with noatime. This seems to be the case only on NetBSD systems; a test on a Linux system showed that mounting with noatime does not affect utime().

Owner

eserte commented Dec 7, 2017

A related issue: golang/go#19293

If the analysis there is right, then atime isn't changed by utime() calls if the filesystem is mounted with noatime. This seems to be the case only on NetBSD systems; a test on a Linux system showed that mounting with noatime does not affect utime().

eserte added a commit that referenced this issue Dec 7, 2017

@eserte eserte changed the title from t/doit.t: utime-related tests fails on some NetBSD systems to t/doit.t: utime-related tests fail on some NetBSD systems Dec 7, 2017

@eserte

This comment has been minimized.

Show comment
Hide comment
@eserte

eserte Dec 28, 2017

Owner

A related issue in Perl's test suite: https://rt.perl.org/Ticket/Display.html?id=132663

Owner

eserte commented Dec 28, 2017

A related issue in Perl's test suite: https://rt.perl.org/Ticket/Display.html?id=132663

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment