-
Notifications
You must be signed in to change notification settings - Fork 41
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
Drop all useless operations when we filter on a field - so we know its value in advance. #775
Conversation
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
…know its value in advance.
4133e02
to
7ca7552
Compare
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!
@@ -248,6 +253,15 @@ def test_nonhermetic_loading(version, dataset_name, record_set_name, num_records | |||
["huggingface-c4/metadata.json", "data", 1, {"data/variant": "en"}], | |||
["huggingface-levanti/metadata.json", "levanti_train", 10, None], | |||
["huggingface-open-hermes/metadata.json", "default", 3, None], | |||
# This dataset will timeout if the following feature is broken: mlcroissant |
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.
Shall we add a meaningful error message somewhere?
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.
I would rather keep it simple with a comment - otherwise it means intercepting pytest's timeout or create a timeout, etc
0136e47
to
908cb8a
Compare
908cb8a
to
4bcc63a
Compare
That way, we can:
Instead of:
I also added a non-hermetic test which should timeout if there's a regression on this feature.