-
Notifications
You must be signed in to change notification settings - Fork 757
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
Update ci tests for mnist example #684
Conversation
9fdbc7b
to
aa159ab
Compare
602e20e
to
625f79a
Compare
71bf729
to
5ba5b0e
Compare
/retest |
That's strange.. Cannot get the trainning data from tensorflow, caused by network issue?
|
d14b442
to
3fcdd4a
Compare
Another problem, seems no permission to upload data to gs ...
|
0adaf2e
to
bc44e57
Compare
Thank you so much @jinchihe ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 18 of 24 files at r1.
Reviewable status: 18 of 24 files reviewed, 1 unresolved discussion (waiting on @jinchihe, @lluunn, and @texasmichelle)
mnist/training/GCS/kustomization.yaml, line 9 at r1 (raw file):
gcr.io/kubeflow-ci/mnist/model
How come we are using an image in gcr.io/kubeflow-ci and not gcr.io/kubeflow-examples?
Also how come you are changing newTag to latest?
Won't this end up using whatever image was most recently built by the tests? Couldn't that cause problems because we end up using an image that was built by a presubmit which made broken changes to the serving code.
Should we instead leave this image as gcr.io/kubeflow-examples/mnist/model and point to a well defined newTag.
This would correspond to that last known good image and have to be updated manually. So it could get out of sync with the code checked iuntil we automate updating it).
Could our tests run kustomsize edit set image to point to a specific image in kubeflow-ci corresponding to the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apologies for the day last week was a holidy
Reviewable status: 18 of 24 files reviewed, 1 unresolved discussion (waiting on @jinchihe, @lluunn, and @texasmichelle)
69cdaf8
to
a067214
Compare
a067214
to
8d14433
Compare
Hello @jlewi Thanks for your comments. Updated as below:
|
/lgtm |
[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 |
fixes: #677
The PR is going to:
Change tfjob_test.py to use pytest to support better reporting of test results
Change deploy_test.py change to use pytest
Replace the ksonnet workflow with the use of python to define the workflow
Removed GOOGLE_APPLICATION_CREDENTIALS setting and using work identity.
This change is