Add integration test for multiprocessing usage #2046
+98
−0
Conversation
This file contains 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
meatballhat
changed the title
in which the setup spawns a child process that accepts a multiprocessing Connection and Lock which are used in each prediction. The intent of this test is to ensure Cog plays nicely with any predictor that uses these features of multiprocessing, especially in combination with a Path output, since these have been common elements of known failures.
meatballhat
force-pushed
the
multiprocessing-test
branch
from
d6a9946
to
160ef58
Compare
nickstenning
reviewed
Nov 7, 2024
| print(f"Getting ready for some serious ponginggg ({i+1}%)") | ||
| time.sleep(0.001 + (0.001 * (i + 1))) | ||
|
|
||
| print("ITS PONGIN TIME") |
nickstenning
approved these changes
Nov 7, 2024
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.
in which the setup spawns a child process that accepts a multiprocessing Connection and Lock which are used in each prediction.
The intent of this test is to ensure Cog plays nicely with any predictor that uses these features of multiprocessing, especially in combination with a Path output, since these have been common elements of known failures.