-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Switch the API implementation to use the local APIs everywhere we can. #1544
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change LGTM, but looks like you need to also change the associated tests.
Codecov Report
@@ Coverage Diff @@
## master #1544 +/- ##
==========================================
- Coverage 39.52% 39.36% -0.16%
==========================================
Files 50 50
Lines 2548 2548
==========================================
- Hits 1007 1003 -4
- Misses 1375 1378 +3
- Partials 166 167 +1
Continue to review full report at Codecov.
|
@r2d4 ready for another look. |
@minikube-bot test this pleas |
@minikube-bot test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@minikube-bot test this please |
1 similar comment
@minikube-bot test this please |
Was this passing the none driver test? It seems that no entry in ~/.minikube/machines being made now when using the none driver, trying to identify if this is related. |
I think it did, but I guess we lose access to the history now that it's merged :( |
You can click on the "details" button on the merge history message in the PR and see the test history. Looks like the None driver was passing https://storage.googleapis.com/minikube-builds/logs/1544/Linux-None.txt |
No description provided.