Skip to content
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

Jump to bottom

os: TestChtimes fails on netbsd #19293

Closed
bradfitz opened this issue Feb 26, 2017 · 10 comments
Closed

os: TestChtimes fails on netbsd #19293

bradfitz opened this issue Feb 26, 2017 · 10 comments
Labels
FrozenDueToAge OS-NetBSD Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone
Go1.11

Comments

@bradfitz
Copy link
Contributor

The NetBSD builders are back up and running (now on GCE instead of dedicated machine singular) and are failing with:

ok  	net/url	0.009s
--- FAIL: TestChtimes (0.00s)
	os_test.go:1067: AccessTime didn't go backwards; was={486366670 63623730007 6480864}, after={486366670 63623730007 6480864}
--- FAIL: TestChtimesDir (0.00s)
	os_test.go:1067: AccessTime didn't go backwards; was={486603380 63623730007 6480864}, after={486603380 63623730007 6480864}
FAIL
FAIL	os	0.363s

(NetBSD 7.0)

/cc @bsiegert @mdempsky
@bradfitz bradfitz added this to the Go1.9 milestone Feb 26, 2017
@bradfitz
Copy link
Contributor Author

NetBSD's stat(2) manpage says:

      st_atime   Time when file data was last accessed.  Changed by the
                 mknod(2), utimes(2), and read(2) system calls.

And the chtimes manpage says:

     The nanosecond fields for utimens(), lutimens(), futimens(), and
     utimensat() can be set to the special value UTIME_NOW to set the current
     time, or to UTIME_OMIT to let the time unchanged (this allows changing
     access time but not modification time, and vice-versa).

Those magic nanosecond values are:

https://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/sys/stat.h

/*
 * Special values for utimensat and futimens
 */
#define UTIME_NOW	((1 << 30) - 1)
#define UTIME_OMIT	((1 << 30) - 2)
#endif

To change atime, do we need to do two system calls, once for modtime first, and then one for atime only with mtime set to UTIME_OMIT?

@gopherbot
Copy link

CL https://golang.org/cl/37492 mentions this issue.

gopherbot pushed a commit that referenced this issue Feb 26, 2017
@bradfitz
os: skip atime-going-backwards test on NetBSD for now
4b22485 
That failing test is preventing other tests from running.
Let's see what else is broken.

Updates #19293

Change-Id: I4c5784be94103ef882f29dec9db08d76a48aff28
Reviewed-on: https://go-review.googlesource.com/37492
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Matt Layher <mdlayher@gmail.com>
@bradfitz bradfitz added the Testing An issue that has been verified to require only test changes, not just a test failure. label May 24, 2017
@bradfitz bradfitz modified the milestones: Go1.10, Go1.9 Jun 7, 2017
@bradfitz bradfitz self-assigned this Nov 28, 2017
@bradfitz
Copy link
Contributor Author

I can no longer reproduce this with NetBSD 8-BETA, our new minimum version requirement for NetBSD.

So maybe it was fixed since we last saw it.

/cc @bsiegert

@bradfitz
Copy link
Contributor Author

(If so, all that would remain here is removing the t.Skip in pkg os TestChtimes)

@gopherbot
Copy link

Change https://golang.org/cl/80875 mentions this issue: os: remove skipped test on netbsd

@bradfitz bradfitz reopened this Nov 30, 2017
@bradfitz bradfitz modified the milestones: Go1.10, Go1.11 Nov 30, 2017
@bradfitz
Copy link
Contributor Author

Reverting.

I was wrong. It still fails on the builders.

I don't know what's different about my VMWare VM, but on GCE it fails.

@bradfitz
Copy link
Contributor Author

bradfitz commented Dec 1, 2017 •
edited

Oh, I figured it out. I tried the Timespec.Nsec UTIME_OMIT thing above, but this bug is actually because our builders run:

/sbin/mount -u -o async,noatime /

... at boot, to speed up builds. We do the same on almost all our Unix builders, with whatever spelling of the command they use.

On NetBSD, though, setting "noatime" seems to also disable explicit utimesat calls. Other BSDs seem to interpret "noatime" as only affecting the implicit atime updates from reading files.

I verified on my NetBSD VM:

localhost# go test -v -run=Chtimes
=== RUN   TestChtimes
--- PASS: TestChtimes (0.00s)
        os_test.go:1170: pre atime: 2017-11-30 19:19:15.960439676 -0800 PST
        os_test.go:1171: pre mtime: 2017-11-30 19:19:15.960610089 -0800 PST
        os_test.go:1186: post atime: 2017-11-30 19:19:14.960439676 -0800 PST (1512098354960439676)
        os_test.go:1187: post mtime: 2017-11-30 19:19:14.960610089 -0800 PST (1512098354960610089)
=== RUN   TestChtimesDir
--- PASS: TestChtimesDir (0.00s)
        os_test.go:1170: pre atime: 2017-11-30 19:19:15.961043733 -0800 PST
        os_test.go:1171: pre mtime: 2017-11-30 19:19:15.961043733 -0800 PST
        os_test.go:1186: post atime: 2017-11-30 19:19:14.961043733 -0800 PST (1512098354961043733)
        os_test.go:1187: post mtime: 2017-11-30 19:19:14.961043733 -0800 PST (1512098354961043733)
PASS
ok      os      0.004s
localhost# /sbin/mount -u -o async,noatime /
localhost# go test -v -run=Chtimes
=== RUN   TestChtimes
--- FAIL: TestChtimes (0.00s)
        os_test.go:1170: pre atime: 2017-11-30 19:19:22.214177347 -0800 PST
        os_test.go:1171: pre mtime: 2017-11-30 19:19:22.214352718 -0800 PST
        os_test.go:1186: post atime: 2017-11-30 19:19:22.214177347 -0800 PST (1512098362214177347)
        os_test.go:1187: post mtime: 2017-11-30 19:19:21.214352718 -0800 PST (1512098361214352718)
        os_test.go:1198: AccessTime didn't go backwards; was=2017-11-30 19:19:22.214177347 -0800 PST, after=2017-11-30 19:19:22.214177347 -0800 PST
=== RUN   TestChtimesDir
--- FAIL: TestChtimesDir (0.00s)
        os_test.go:1170: pre atime: 2017-11-30 19:19:22.214812902 -0800 PST
        os_test.go:1171: pre mtime: 2017-11-30 19:19:22.214812902 -0800 PST
        os_test.go:1186: post atime: 2017-11-30 19:19:22.214812902 -0800 PST (1512098362214812902)
        os_test.go:1187: post mtime: 2017-11-30 19:19:21.214812902 -0800 PST (1512098361214812902)
        os_test.go:1198: AccessTime didn't go backwards; was=2017-11-30 19:19:22.214812902 -0800 PST, after=2017-11-30 19:19:22.214812902 -0800 PST
FAIL
exit status 1
FAIL    os      0.004s

So I guess I'll just skip that test on NetBSD and close this bug.

@bsiegert, @krytarowski, @zoulasc, I assume that's expected behavior, but let me know if not.

@gopherbot
Copy link

Change https://golang.org/cl/81355 mentions this issue: os: ignore Chtimes test failure on NetBSD if fs mounted noatime

@krytarowski
Copy link
Contributor

Hmm, From a quick look I don't see a relation between MNT_NOATIME and lack of precise time.

I think we should update to syscalls from NetBSD 8.0 (so switch to: __stat50). There were changes in time functions like extending to 64-bit time_t. At some point we have added POSIX interfaces. Some subtle bugs can go from mixing old syscalls (they appear to be from NetBSD 5.) and assume behavior from 8.0.

@bradfitz
Copy link
Contributor Author

bradfitz commented Dec 1, 2017

@krytarowski, this isn't about precise time. Ignore the nanoseconds part. The key part is:

On NetBSD, though, setting "noatime" seems to also disable explicit utime* calls. Other BSDs seem to interpret "noatime" as only affecting the implicit atime updates from reading files.

@eserte eserte mentioned this issue Dec 7, 2017
Closed
@golang golang locked and limited conversation to collaborators Dec 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge OS-NetBSD Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
None yet
Milestone
Go1.11
Development

No branches or pull requests
3 participants
@bradfitz @krytarowski @gopherbot