Remove ~/repo before moving Cloud SDK components there #18840
Merged
Conversation
This file contains hidden or 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
|
Labelling this PR as size/XS |
|
This should work fine. Haven't run into it yet because we normally wipe the workspace between runs. |
|
GCE e2e test build/test passed for commit 375f4df. |
|
cc @k8s-oncall. Manually merging to unbreak kubernetes-soak-continuous-e2e-gke |
j3ffml
added a commit
that referenced
this pull request
Dec 18, 2015
Remove ~/repo before moving Cloud SDK components there
k8s-github-robot
referenced
this pull request
Dec 18, 2015
…8840-upstream-release-1.1 Auto commit by PR queue bot
shyamjvs
referenced
this pull request
in shyamjvs/kubernetes
Dec 1, 2016
…pick-of-#18840-upstream-release-1.1 Auto commit by PR queue bot
shouhong
referenced
this pull request
in shouhong/kubernetes
Feb 14, 2017
…pick-of-#18840-upstream-release-1.1 Auto commit by PR queue bot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
~/repomight have existed from a prior run, if we're doing jobs in sequence and not cleaning up in between.Not sure if this is the right way to fix this problem; I'm open to suggestions.
Failure e.g. http://kubekins.dls.corp.google.com/view/Upgrade%20Test%20-%20GKE/job/kubernetes-upgrade-gke-1.0-master-step5-upgrade-cluster/21/console