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

Add test for tf-job-simple prototype #1010

Merged
merged 4 commits into from Jun 15, 2018
Merged

Add test for tf-job-simple prototype #1010

merged 4 commits into from Jun 15, 2018

Conversation

ankushagarwal
Copy link
Contributor

@ankushagarwal ankushagarwal commented Jun 15, 2018

tf_job_simple_test.py tests the tf-job-simple prototype by creating a tfjob from that prototype and checking that the appropriate pods and service accounts get created

Fixes #462


This change is Reviewable

@ankushagarwal ankushagarwal changed the title Add test for tf-job-simple prototype WIP - Add test for tf-job-simple prototype Jun 15, 2018
@ankushagarwal ankushagarwal changed the title WIP - Add test for tf-job-simple prototype Add test for tf-job-simple prototype Jun 15, 2018
@ankushagarwal
Copy link
Contributor Author

/cc @lluunn @kunmingg

This is ready for review

@k8s-ci-robot k8s-ci-robot requested a review from lluunn June 15, 2018 18:14
@retry(wait_fixed=5000, stop_max_attempt_number=20)
def wait_for_tf_job():
out = util.run(["kubectl", "get", "pods", "-l",
"tf_job_name=mycnnjob", "-ndefault"])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If namespace is default, do we need to delete them? I guess jobs will gone after finish, how about the service?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will be deleting the cluster at the end so I did not bother deleting this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we using kubeflow-testing cluster in kubeflow-ci?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we'll be creating a new cluster for every test

@lluunn
Copy link
Contributor

lluunn commented Jun 15, 2018

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lluunn

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit f36cf39 into kubeflow:master Jun 15, 2018
@ankushagarwal ankushagarwal deleted the e2e-test-tf-job-simple branch June 18, 2018 23:29
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
* Add test for tf-job-simple prototype

Fixes kubeflow#462

* Update

* Update

* Update
yanniszark pushed a commit to arrikto/kubeflow that referenced this pull request Feb 15, 2021
* feat: Do not inject sh -c when it exists

Signed-off-by: Ce Gao <gaoce@caicloud.io>

* fix: Add test cases

Signed-off-by: Ce Gao <gaoce@caicloud.io>

* fix: Add test cases

Signed-off-by: Ce Gao <gaoce@caicloud.io>
surajkota pushed a commit to surajkota/kubeflow that referenced this pull request Jun 13, 2022
* Use a configmap generator for the spawner_ui_config.yaml

* Using a configmap generator is a bit cleaner because we can store
  the configuration file in a external file rather than inlining it in
  the config map.

* Using a configmap generator also has the advantage that kustomize will
  generate a unique name based on a hash of the content.

  * This has the advantage that if a user updates the config, the hash
    would change so deployments would automatically be redeployed in order
    to pick up the config changes.

* Also update the default image used in the configmap to fix kubeflow#1010

* Rebase and regenerate the tests.

* * The deployment for the UI needs to use the original name of
  the jupyter web app config map without the prefix/suffix.

* Update expected tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants