-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix bug for the component build with requirements #320
fix bug for the component build with requirements #320
Conversation
/retest |
2 similar comments
/retest |
/retest |
/test presubmit-unit-test |
/lgtm |
It's a bit alarming that the feature was checked in in a broken state and tests did not catch it. I'm partially to blame for that since I did not notice this problem. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gaoning777 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The unit tests do not run the docker command, thus missing the bug. |
…code (kubeflow#320) * Create a batch job to allow manual runs of auto-deploying the latest cluster. * * Add a Makefile * Pass in zone. * Move to us-east1-b becasue of kubeflow#321 * Fix zones. * Make zone required.
…ubeflow#320) * v1alpha2 spec for predict,explain,transform * Convert from knative configuration to service * Fix service resource tests * Fix service reconciler tests * Fix service finalizer * Fix controller test * Rename to predictor service * Fix conflicts * Watch knative service * Fix predictor route name * Fix integration test * structure reconciler for different endpoints * refactor and placeholder for explainer/transformer * shorten code :) * Use enum instead of string * use string constant for default/canary * Fix canary finalizer name * Use endpoint verb for route name
This change is