Skip to content
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

Closed
3 of 7 tasks
jlewi opened this issue Dec 18, 2017 · 4 comments
Closed
3 of 7 tasks

E2E Testing For Kubeflow. #38

jlewi opened this issue Dec 18, 2017 · 4 comments
Assignees

Comments

@jlewi
Copy link
Contributor

jlewi commented Dec 18, 2017

We need to setup continuous E2E testing for google/kubeflow

  • Create a basic an E2E test
    • Deploy and verify JupyterHub is working
    • Deploy and verify TfJob is working
    • Verify TfServing is working
  • Setup prow for google/kubeflow
    • Setup presubmit tests
    • Setup postsubmit tests

I think it makes sense to write the E2E test first and then once we have it we can setup prow integration.

@jlewi jlewi self-assigned this Dec 18, 2017
@foxish
Copy link
Contributor

foxish commented Dec 18, 2017

Related: kubernetes/test-infra#6011

@jlewi
Copy link
Contributor Author

jlewi commented Dec 29, 2017

Track progress following these instructions to setup prow.

Status 01/04

  • Prow jobs are triggering
  • Need to add k8s/robot to google/kubeflow

jlewi added a commit that referenced this issue Jan 5, 2018
* 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
@jlewi jlewi added this to the Kubecon Europe milestone Jan 10, 2018
jlewi added a commit that referenced this issue Jan 10, 2018
* 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.
@jlewi jlewi mentioned this issue Jan 29, 2018
5 tasks
@jlewi
Copy link
Contributor Author

jlewi commented Feb 4, 2018

presubmits are passing
https://k8s-testgrid.appspot.com/sig-big-data#kubeflow-presubmit

postsubmits don't seem to be running
I think this is the same issue as kubeflow/training-operator#370 i.e we aren't truncating the commit sha when constructing the Argo workflow name.

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.

@jlewi
Copy link
Contributor Author

jlewi commented Mar 7, 2018

We have E2E tests for TFServing.

PR dashboard is setup.

Will open a separate issue for JupyterHub testing.

@jlewi jlewi closed this as completed Mar 7, 2018
kimwnasptd pushed a commit to arrikto/kubeflow that referenced this issue Mar 5, 2019
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Nov 1, 2019
* virtual-service init

* add clusterDomain param

* rm temp file

* remove label

* fix

* remove namespace
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Feb 15, 2021
* 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
VaishnaviHire pushed a commit to VaishnaviHire/kubeflow that referenced this issue Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants