Running functional or integration tests should use the driver built from source instead of the downloaded driver

[obnoxxx]

Third spin-off of #21551

currently, the functional and integration test runs use the downloaded driver instead of one locally built from sources.

This is a possible cause of deceiving false positive test results.

Just like for manual invocation (see #21581 ), the test runs should use the locally built driver instead of a downloaded one.

depends on #21580 as the default build should first produce the driver to be tested.

/kind bug

[medyagh]

@obnoxxx I think you created three issues plz close other ones, and do you mind checking if this has fixed the issue ? (verify)

#21577

[obnoxxx]

@medyagh wrote:

@obnoxxx I think you created three issues
plz close other ones,

I am not sure why only opening of a single issue is alllowed.

All three issues serve different purposes as sub-aspects of a different issue:

#21551 (comment)

In fact, two more issues would be needed to complete the tracking list:

#21551 (comment)

and do you mind checking if this has fixed the issue ? (verify)
#21577

I am testing and will report back.

[obnoxxx]

and do you mind checking if this has fixed the issue ? (verify)
#21577

I am testing and will report back.

@medyagh I do in fact have a question how to properly test this, i. e. how can I tell
definitively whether a driver in ˜/.minikube/bin is downloaded or a. local build?

I guess looking at the timestamp is not sufficient, right?

[medyagh]

MINIKUBE_HOME=/tmp/test1

"make functional"

check the logs
docker-machine-kvm... --version

[obnoxxx]

@medyagh wrote:

MINIKUBE_HOME=/tmp/test1

"make functional"

check the logs docker-machine-kvm... --version

I tried this but I am not quite clear yet about the conclusion:

I ran the following from a current master checkout:

$ ls -l $HOME/.minikube/bin/docker-machine-driver-kvm2 
-rwxr-xr-x. 1 obnox obnox 15939488 Sep 17 17:32 /home/obnox/.minikube/bin/docker-machine-driver-kvm2
$ rm -f $HOME/.minikube/bin/docker-machine-driver-kvm2
$ rm -rf tmp/
$ mkdir -p tmp/test
make clean && MINIKUBE_HOME=tmp/test make functional
...
FAIL	k8s.io/minikube/test/integration	4.842s
FAIL
$ echo $?
0
$ ls -l tmp/test/
total 0
$ ls -l $HOME/.minikube/bin/docker-machine-driver-kvm2 
ls: cannot access '/home/obnox/.minikube/bin/docker-machine-driver-kvm2': No such file or directory

I. e.:

1. the MINIKUBE_HOME remains empty after the test run -- is that expected?
2. no new driver is downloaded to ˜/.minikube/bin