Closed MATRIX4284 closed 4 years ago
Hi @MATRIX4284. 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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign johnugeorge
You can assign the PR to them by writing /assign @johnugeorge
in a comment when ready.
The full list of commands accepted by this bot can be found here.
/ok-to-test
@MATRIX4284: The following test failed, say /retest
to rerun them all:
Test name | Commit | Details | Rerun command |
---|---|---|---|
kubeflow-pytorch-operator-presubmit | 0a7e04f9ad5db107dc78f6e4f7a3654839738962 | link | /test kubeflow-pytorch-operator-presubmit |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
Added the required Dockerfile For mitigating the issue #245
image name gcr.io//pytorch_dist_mnist:latest wil cause the image pull to fail in case of non gcp users.
So included the yaml specs with the local image i.e. kubeflow/pytorch-dist-mnist-test:1.0.