[DO NOT MERGE] debug

[tenzen-y]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

• Docs included if any changes are user facing

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tenzen-y

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:

• OWNERS [tenzen-y]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coveralls]

Pull Request Test Coverage Report for Build 6125433423

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 12 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.1%) to 42.77%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controller.v1/tensorflow/tfjob_controller.go	4	75.27%
pkg/controller.v1/mpi/mpijob_controller.go	8	80.48%

Totals
Change from base Build 6125431529:	-0.1%
Covered Lines:	3736
Relevant Lines:	8735

---

💛 - Coveralls

[andreyvelich]

@tenzen-y Any ideas why MXNet example could fail during our E2E ?
I tested locally, and it also stuck in Running state.

[tenzen-y]

@tenzen-y Any ideas why MXNet example could fail during our E2E ? I tested locally, and it also stuck in Running state.

Have you seen the failure in the master branch as well?

[andreyvelich]

@tenzen-y Any ideas why MXNet example could fail during our E2E ? I tested locally, and it also stuck in Running state.

Have you seen the failure in the master branch as well?

I think so, let me try to rebase my PR.