Repository navigation
Support parallel Crystalball evaluation - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
parallel_testsworker variablesProblem
Each parallel worker received the complete prediction. In the end-to-end reproduction, a serial run selected 9 examples, but two workers ran 18 examples in total. This caused duplicate work and could cause test resource conflicts.
Verification
bundle exec rspec spec features(308 examples, 0 failures)bundle exec rubocop(192 files, no offenses)bundle exec yard --fail-on-warningbundle exec rake buildScope
This PR fixes prediction evaluation. Parallel map generation has a different problem: workers compact and write map fragments independently. That work should use a separate change.