-
Notifications
You must be signed in to change notification settings - Fork 74.2k
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
Switch IteratorTest to use TF combinations #32599
Switch IteratorTest to use TF combinations #32599
Conversation
fa2fe76
to
4a9296b
Compare
"b": ([1], []) | ||
}), | ||
) | ||
@combinations.generate(combinations.times( |
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.
As a rule of thumb, we have agreed on the tf.data team that going forward we should not used parametrized tests that require lambda
parameters and instead create separate unit tests. Could you please split this tests into separate tests, one for each test case? Thank you.
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.
Sure, will do it.
4a9296b
to
de66e7b
Compare
@gbaned An error happened while migrating the change for the internal check. Could you please help re-trigger the internal check? Thanks! |
PiperOrigin-RevId: 270286442
This PR switch
IteratorTest
to use TF combinations.