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

mnist test isn't part of CI #597

Closed
jlewi opened this issue May 21, 2018 · 3 comments
Closed

mnist test isn't part of CI #597

jlewi opened this issue May 21, 2018 · 3 comments

Comments

@jlewi
Copy link
Contributor

jlewi commented May 21, 2018

An mnist test was added but this isn't integrated with our CI system.
https://github.com/kubeflow/tf-operator/tree/master/test/e2e/dist-mnist

Ideally we'd run this as part of an Argo workflow that would build and deploy the latest version of the TFJob operator

/cc @ScorpioCPH
/priority p2

@jlewi
Copy link
Contributor Author

jlewi commented Jul 3, 2018

Adding this to 0.3.0 so its on our radar. I think we need to figure out a plan with regards to testing in order to get TFJob operator to the next level of reliability.

@carmine carmine added this to the 0.4.0 milestone Nov 6, 2018
@jlewi jlewi removed this from the 0.4.0 milestone Feb 4, 2019
@jlewi
Copy link
Contributor Author

jlewi commented Feb 4, 2019

@johnugeorge @richardsliu We have an mnist test in kubeflow/examples. Should we rely on that test and the other E2E tests and remove the mnist test in the TFJob operator repo?

@stale
Copy link

stale bot commented Apr 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this as completed Apr 27, 2020
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

4 participants