Skip Menu |
Report information
Id: 132663
Status: new
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors: slaven [at]

Operating System: (no value)
PatchStatus: (no value)
Severity: low
Type: unknown
Perl Version: (no value)
Fixed In: (no value)

Date: Thu, 28 Dec 2017 16:50:39 +0100
CC: srezic [...]
To: perlbug [...]
Subject: t/io/fs.t failures on NetBSD with noatime mounts
From: slaven [...]
Download (untitled) / with headers
text/plain 1.7k
This is a bug report for perl from, generated with the help of perlbug 1.40 running under perl 5.26.1. ----------------------------------------------------------------- On NetBSD systems t/io/fs.t may fail: # Failed test 30 - atime at t/io/fs.t line 324 # Failed test 31 - mtime at t/io/fs.t line 325 # Failed test 36 - atime at t/io/fs.t line 324 # Failed test 37 - mtime at t/io/fs.t line 325 t/io/fs.t .. Failed 4/61 subtests         (less 5 skipped subtests: 52 okay) Test Summary Report ------------------- t/io/fs.t (Wstat: 0 Tests: 61 Failed: 4)   Failed tests:  30-31, 36-37 Files=1, Tests=61,  1 wallclock secs ( 0.28 usr  0.08 sys +  0.20 cusr  0.11 csys =  0.67 CPU) Result: FAIL This happens if the filesystem where the test files are created s mounted with noatime. Unlike on other OS, it's not possible to change the accesstime using utime* on NetBSD in this situation. A related issue with more discussion: Probably it's best to skip this test if $^O eq 'netbsd' and `mount | grep $tmpdir` shows that noatime is enabled. As a side note, it looks like the mtime test is also failing, but this is a limitation in the test script --- probably the last two fails in check_utime_result() should be differentiated. And as a last note, I don't have a NetBSD machine to test --- the problem was just suspected by me and confirmed by Nigel Horne. ----------------------------------------------------------------- --- Flags: category=core severity=low --- This perlbug was built using Perl 5.20.2 - Mon Sep 18 18:13:32 UTC 2017 It is being executed now by Perl 5.26.1 - Sat Sep 23 09:36:11 CEST 2017. (perl -V output is irrelevant --- sent from a different machine)

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at