This repository has been archived by the owner on Jan 9, 2020. It is now read-only.
forked from apache/spark
-
Notifications
You must be signed in to change notification settings - Fork 118
Parse results of minikube status more rigorously #97
Merged
mccheah
merged 2 commits into
k8s-support-alternate-incremental
from
fix/minikube-version-notifier
Feb 13, 2017
Merged
Parse results of minikube status more rigorously #97
mccheah
merged 2 commits into
k8s-support-alternate-incremental
from
fix/minikube-version-notifier
Feb 13, 2017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior code assumes the minikubeVM status line is always the first row output from minikube status, and it is not when the version upgrade notifier prints an upgrade suggestion message.
+1. I was puzzled by the version update notifier message a few times. |
It would be nice to filter the update notification everywhere. For example, it still prints when you run Alternatively, getting Minikube to point to the |
3c89196
to
c40953a
Compare
@mccheah I added a filter for I'd rather not invest too much in fixing minikube since my personal belief is that we should support running tests against any k8s serverapi, not just minikube. |
Looks fine - will merge. |
ash211
added a commit
that referenced
this pull request
Mar 8, 2017
* Parse results of minikube status more rigorously Prior code assumes the minikubeVM status line is always the first row output from minikube status, and it is not when the version upgrade notifier prints an upgrade suggestion message. * Also filter ip response to expected rows
foxish
pushed a commit
that referenced
this pull request
Jul 24, 2017
* Parse results of minikube status more rigorously Prior code assumes the minikubeVM status line is always the first row output from minikube status, and it is not when the version upgrade notifier prints an upgrade suggestion message. * Also filter ip response to expected rows
ifilonenko
pushed a commit
to ifilonenko/spark
that referenced
this pull request
Feb 25, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #96
Prior code assumes the minikubeVM status line is always the first row output
from minikube status, and it is not when the version upgrade notifier prints
an upgrade suggestion message.