-
Notifications
You must be signed in to change notification settings - Fork 902
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
Follow up making Python tests more deterministic #17272
base: branch-24.12
Are you sure you want to change the base?
Conversation
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.
One suggestion for improving the future usage but it's not a blocker if we decide not to go with it (I'm not sure if we can actually do what I suggest yet).
# Check for usage of default_rng without seeding | ||
default_rng\(\)| | ||
# Check for usage of np.random.seed | ||
np.random.seed\( |
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.
Should we keep this without the parenthesis to forbid usage of np.random.seed in favor of the newer default_rng API?
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.
Ah interesting, NPY002 allows the np.random.seed
callable to exist but complains when it's called. Sure I'll add this back.
Description
Addressing comments in https://github.com/rapidsai/cudf/pull/17008/files#r1823318321 and https://github.com/rapidsai/cudf/pull/17008/files#r1823318898
Didn't touch the
_fuzz_testing
directory because maybe we don't want that to be deterministic?Checklist