-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Updates to Unit Test cases for the TensorFlowTransform #790
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
Conversation
Can you please fix this too? this was my typo. Eric E. had comment on this. One of them is Refers to: test/Microsoft.ML.Tests/ScenariosWithDirectInstantiation/TensorflowTests.cs:122 in 88db7be. [](commit_id = 88db7be, deletion_comment = False) |
zeahmed
left a comment
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.
![]()
| var thrown = false; | ||
| try | ||
| { | ||
| IDataView trans = TensorFlowTransform.Create(env, pixels, model_location, "Output", "Input"); |
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 use Assert.Throws instead of manually try catching. #Pending
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.
for now i am keeping this as-is. will consider using Assert.Throws in future
In reply to: 214481486 [](ancestors = 214481486)
eerhardt
left a comment
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.
![]()
|
Thanks for fixing these up. #Resolved |
Fixes #779
(1) address the additional comments on the original TensorFlowTransform PR
(2) added an additional unit test to verify invalid shapes are being handled correctly