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
[DM-33438] Clean up run_demo.sh #31
Conversation
This script works if I take out the multiprocessing stuff, but with the multiprocessing, I get the following error from the python tests: ___________________________________________________________________ PiplinesCheckTestCase.testExecutionButler (chain='demo_collection_exe') ___________________________________________________________________ self = <test_butler.PiplinesCheckTestCase testMethod=testExecutionButler>
E AssertionError: 21 != 13 tests/test_butler.py:101: AssertionError self = <test_butler.PiplinesCheckTestCase testMethod=testExecutionButler>
E AssertionError: 21 != 13 tests/test_butler.py:101: AssertionError |
That test is saying that the number of datasets created in the EXECUTION BUTLER bit of code (the first 3 pipetask calls using $NODE) is equal to the number of datasets created by the QUNTUM BACKED BUTLER bit of code (the second set of 3 pipetask calls using $NODE). |
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.
This looks good. There is a small possibility that the two parallel processes hitting sqlite would fall over each other but given that the second run is using the graph and not the sqlite at all and we only have two processes, I think this will almost certainly be fine. cc/ @andy-slac
No description provided.