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
E2E Testing For Kubeflow. #38
Comments
Related: kubernetes/test-infra#6011 |
Track progress following these instructions to setup prow.
Status 01/04
|
* test_deploy.py is a python script that * Creates a ksonnet app * Deploys Kubeflow * Does some basic checks to see if the Kubeflow deployment is healthy test_deploy.py will be used to create continuous E2E tests for Kubeflow. * Log output and test results are written to a local directory * In a follow on PR we will add a binary to copy all the outputs from the local directory to Gubernator. This way most steps in the test don't need to deal with GCS. * First piece of #38 (E2E test for Kubeflow) * Add a pylintrc file
* Create a binary to launch an Argo workflow and wait for it to finish. * This binary is intended to be run by our Prow jobs to trigger our E2E tests. * Part of #38 We create the started and finished artifacts for gubernator in the script that launches the workflow.
presubmits are passing postsubmits don't seem to be running To fix this we should probably modify kubeflow/kubeflow to pull run_workflow_e2e.py from kubeflow/testing once kubeflow/testing#9 is submitted. That pr should fix this issue. |
We have E2E tests for TFServing. PR dashboard is setup. Will open a separate issue for JupyterHub testing. |
* virtual-service init * add clusterDomain param * rm temp file * remove label * fix * remove namespace
* bayesian optimization draft * add matern kernel and two other acquisition functions * modify the code structure and add Dockerfile and k8s manifest * fix typos in manifest files * add build and deploy test * fix errors in run-tests
Add Replicas to Deployment
We need to setup continuous E2E testing for google/kubeflow
I think it makes sense to write the E2E test first and then once we have it we can setup prow integration.
The text was updated successfully, but these errors were encountered: