Skip to content

Fix non-deterministic ordering assumption in input_pipeline_test. #222

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.

Sign up for GitHub

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

Open
copybara-service wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix non-deterministic ordering assumption in input_pipeline_test. #222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions vmoe/data/input_pipeline_test.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,9 +119,10 @@ def test_eval(self):
# Eval data has a '__valid__' field, since fake examples were added.
self.assertSetEqual(set(data[0].keys()),
{'x', 'y', input_pipeline.VALID_KEY})
# Eval data is not shuffled, and the fake data corresponds to the first
# element.
self.assertTupleEqual(tuple(data[0]['x']), (0, 1, 2, 0, 0))
# Eval data has valid elements (order may vary due to non-deterministic
# parallel mapping) and fake elements at the end.
self.assertSequenceEqual(sorted(data[0]['x'][:3]), (0, 1, 2))
self.assertTupleEqual(tuple(data[0]['x'][3:]), (0, 0))
self.assertTupleEqual(tuple(data[0][input_pipeline.VALID_KEY]),
(True, True, True, False, False))

Expand Down
Loading