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

reconcile tensorflow serving version #409

Merged

Conversation

hougangliu
Copy link
Member

@hougangliu hougangliu commented Dec 6, 2018

Fixes: #408


This change is Reviewable

@k8s-ci-robot
Copy link
Contributor

Hi @hougangliu. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@@ -17,12 +17,14 @@ MODEL_COMPONENT=pets-model
MODEL_PATH=/mnt/exported_graphs/saved_model
MODEL_STORAGE_TYPE=nfs
NFS_PVC_NAME=pets-pvc
TF_SERVING_VERSION=`kubectl -n kubeflow exec -ti tf-training-job-master-0 -- python -c 'from __future__ import print_function;import tensorflow;print(tensorflow.__version__, end="")'`
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a cleaner way to handle this? Why do we wait until runtime to get the TF version? Shouldn't this be determined by the code that gets checked in?
https://github.com/kubeflow/examples/blob/master/object_detection/docker/Dockerfile.training#L45

So can't we just have the code pin consistent version of TF across the example?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for your comment. Agree with you. Since default OBJ_DETECTION_IMAGE tensorflow version is 1.10.0, we pin consistent version 1.10.0 of TF across the example.
Updated.

Since default OBJ_DETECTION_IMAGE tensorflow version is 1.10.0, we
pin consistent version 1.10.0 of TF across the example.

Fixes: kubeflow#408
@hougangliu hougangliu force-pushed the reconcile_tf_serving_version branch from 85977ff to 9ce8a9f Compare December 8, 2018 03:35
@jlewi
Copy link
Contributor

jlewi commented Dec 8, 2018

/ok-to-test
/lgtm
/approve

@hougangliu I think you should have recieved an invite to join the GitHub Kubeflow org; if you accept it that will allow you to trigger the tests.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

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 fc5a85b into kubeflow:master Dec 8, 2018
govindKAG pushed a commit to govindKAG/examples that referenced this pull request Feb 27, 2019
Since default OBJ_DETECTION_IMAGE tensorflow version is 1.10.0, we
pin consistent version 1.10.0 of TF across the example.

Fixes: kubeflow#408
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.

3 participants