integration test: jenkins running the wrong binary but showing the right commit id #5605
Description
while doing this PR: #5530
I noticed a spooky behaviour that my integraiton tests would pass on local machine but fail horribly the jenkins
The logs showed that it had the right commit :
https://storage.googleapis.com/minikube-builds/logs/5530/KVM_Linux.txt
Started by upstream project "Build_Cross" build number 8647
originally caused by:
GitHub pull request #5530 of commit 390992571fbad36aff04fd08fd59e6d5b8a36415, no merge conflicts.
Running as SYSTEM
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the bui
but I suspected that it actually runs the right binary !
I added a logging message and I expected it to see in the logs:
exit.WithError("Failed to update cluster<--Temproary logging-->", err)
however I got this error that doesn't belong to that code !
Details
X Failed to update cluster: starting kubelet command: "/bin/bash -c "sudo systemctl daemon-reload && sudo systemctl start kubelet"" output: "\n** stderr ** \nusage: sudo -h | -K | -k | -V\nusage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]\nusage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]\n [command]\nusage: sudo [-AbEHknPS] [-C num] [-g group] [-h host] [-p prompt] [-T timeout]\n [-u user] [VAR=value] [-i|-s] []\nusage: sudo -e [-AknS] [-C num] [-g group] [-h host] [-p prompt] [-T timeout]\n [-u user] file ...\n\n** /stderr **": Process exited with status 1
10:42:40 *
10:42:40 * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
Also : I see the following failed to delete in the beggining of the script
11:03:34 >> Cleaning up after previous test runs ...
11:03:34 * Cleaning stale test root: /home/jenkins/minikube-integration/linux-amd64-kvm2-5225-12310-98e906446c6a6a4dadd13b0a6537dc9f1b3d895a
11:03:34 rmdir: failed to remove '/home/jenkins/minikube-integration/linux-amd64-kvm2-5225-12310-98e906446c6a6a4dadd13b0a6537dc9f1b3d895a': Directory not empty
11:03:34 test.json
11:03:34 test.out
11:03:34 * Cleaning stale test root: /home/jenkins/minikube-integration/linux-amd64-kvm2-5225-29692-c3c62a451c0b089f352485fa9bf668b86bdb5ba4
11:03:34 rmdir: failed to remove '/home/jenkins/minikube-integration/linux-amd64-kvm2-5225-29692-c3c62a451c0b089f352485fa9bf668b86bdb5ba4': Directory not empty
11:03:34 tests.json
11:03:34 * Cleaning stale test root: /home/jenkins/minikube-integration/linux-amd64-kvm2-5225-603-9e58a9a0b93e0f3ba132b98f5ef2df806bf7898b
11:03:34 rmdir: failed to remove '/home/jenkins/minikube-integration/linux-amd64-kvm2-5225-603-9e58a9a0b93e0f3ba132b98f5ef2df806bf7898b': Directory not empty
11:03:34 test.json
11:03:34 * Cleaning stale test root: /home/jenkins/minikube-integration/linux-amd64-none-5225-21635-079c256655b4f84a00b505d8f53b396b52e22885
11:03:34 rmdir: failed to remove '/home/jenkins/minikube-integration/linux-amd64-none-5225-21635-079c256655b4f84a00b505d8f53b396b52e22885': Directory not empty