Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Traceback (most recent call last): File "<embedded stdlib>/unittest/case.py", line 59, in testPartExecutor yield File "<embedded stdlib>/unittest/case.py", line 605, in run testMethod() File "/build/work/07c770a45d8136487a6531d96b0354730923/google3/runfiles/google3/third_party/tensorflow/python/eager/profiler_test.py", line 56, in test_profile self.assertIn('Mul:Mul', events) File "<embedded stdlib>/unittest/case.py", line 1089, in assertIn self.fail(self._formatMessage(msg, standardMsg)) File "/build/work/07c770a45d8136487a6531d96b0354730923/google3/runfiles/google3/third_party/py/absl/testing/absltest.py", line 1767, in fail return super(TestCase, self).fail(self._formatMessage(prefix, msg)) File "<embedded stdlib>/unittest/case.py", line 670, in fail raise self.failureException(msg) AssertionError: 'Mul:Mul' not found in frozenset({'ExecutorState::Process', 'three_times_five', 'mul:Mul', 'SessionRun', 'ExecutorDoneCallback'})
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.
can you please check above error ?
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.
@rthadur
the error you have mentioned
seems to be unrelated to the change in this PR.
The change in this PR merely skips the check on line 51/53 on the ROCm platform.
The assert that is firing is on line 56/58, and the reason seems to be a change in the event name (
mul:Mul
vsMul:Mul
). That does not seem related to the change in this PRThere 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.
thank you