-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Our ksonnet sometimes throws "SIGSEGV: segmentation violation" failing deployment #241
Comments
Maybe it is possible to add ksonnet flags like --api-spec for example to bootstraper image flags to have more freedom. |
I also met the problem today, and that can be reproduced 100%, the deployment has been blocked.
From the ksonnet/ksonnet#883, seems the problem has been fixed in the ks v0.13.1. I tested, that's passed with the new ks. I think we need to upgrade ks in deployer component. |
Assuming that this has been resolved since it has been idle for a long time. Please re-open if it is not the case. |
Thanks @jinchihe. Apologies for closing this. |
…#241) The mentioned labels are very close to the threshold that github uses to determine whether to use black or white foreground text. By darkening them slightly, the foreground switches to white, and the labels become more readable.
* add cmpopts dependency * Revert "add cmpopts dependency" This reverts commit 388d12cc3aca81abad6e840c18a00d55b49841d2. * dep ensure -add github.com/google/go-cmp/cmp/cmpopts@v0.3.0 * Revert "dep ensure -add github.com/google/go-cmp/cmp/cmpopts@v0.3.0" This reverts commit 8b5e21e10d322bc20761b578a53c5d89bbd1cfa9. * dep ensure -add github.com/google/go-cmp/cmp/cmpopts@6f77996f0c42f7b84e5a2b252227263f93432e9b (use specific version to match knative)
update changes the rpm repository ids
https://gubernator.k8s.io/build/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/232/presubmit-e2e-test-gce-minikube/129/
KSonnet issue: ksonnet/ksonnet#883
Resolved in https://github.com/ksonnet/ksonnet-lib/releases/tag/v0.1.12
The text was updated successfully, but these errors were encountered: