Fix for issue #3044 - mounted timestamps incorrect with windows host

[ngoozeff]

Test cases & resolution for #3044.

Original Behavior:

go test ./test/integration --tags integration -binary c:\programdata\chocolatey\bin\minikube.exe --minikube-start-args "--vm-driver hyperv" -run TestFunctional/Mounting --minikube-mount-args "--ip 192.168.128.103" -v
=== RUN   TestFunctional
=== RUN   TestFunctional/Mounting
=== PAUSE TestFunctional/Mounting
=== CONT  TestFunctional/Mounting
--- FAIL: TestFunctional (7.82s)
    --- FAIL: TestFunctional/Mounting (25.03s)
        mount_test.go:131: Invalid access time
              File: /mount-9p/fromhost
              Size: 5           Blocks: 1          IO Block: 65536  regular file
            Device: 10008eh/1048718d    Inode: 7           Links: 1
            Access: (0666/-rw-rw-rw-)  Uid: (    0/    root)   Gid: (    0/    root)
            Access: 1970-01-01 00:00:00.000000000 +0000
            Modify: 1970-01-01 00:00:00.000000000 +0000
            Change: 1970-01-01 00:00:00.000000000 +0000
             Birth: -
FAIL
FAIL    k8s.io/minikube/test/integration        33.428s

With this fix:

go test ./test/integration --tags integration -binary ..\..\out\minikube-windows-amd64.exe --minikube-start-args "--vm-driver hyperv" -run TestFunctional/Mounting --minikube-mount-args "--ip 192.168.128.103" -v
=== RUN   TestFunctional
=== RUN   TestFunctional/Mounting
=== PAUSE TestFunctional/Mounting
=== CONT  TestFunctional/Mounting
--- PASS: TestFunctional (7.61s)
    --- PASS: TestFunctional/Mounting (26.89s)
PASS
ok      k8s.io/minikube/test/integration        35.102s

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[minikube-bot]

Can one of the admins verify this patch?

[tstromberg]

@minikube-bot OK to test

[ngoozeff]

@tstromberg I've managed to reproduce these failures on my linux box. I think it might be related to the msize default for the mount command being too large for the tests. I'm currently investigating.

[tstromberg]

@minikube-bot OK to test

[tstromberg]

Do you mind addressing the merge conflict? I'd like to see about merging this if it's still viable. My apologies for the unnecessarily long delay in reviewing this PR.

[ngoozeff]

Will do - I'll take a look over the weekend.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ngoozeff
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: dlorenc

If they are not already assigned, you can assign the PR to them by writing /assign @dlorenc in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment