Fixed the SA test breaking in pycc mode where the data process was not actually running before assertions were made #562
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.
This should ensure that test does not prematurely try to continue down the road with assertions, when the process launched through create_data_process() is not actually running.
Note that we could not use EventSubscriber() since the process id used to listen is actually inside the data process returned by the create_data_process(). So we cannot setup the EventSubscriber before executing a create_data_process(). On the other hand, we could not use the EventSubscriber() after the create_data_process(), because then we would not be able to catch the superfast process launches.
So instead of looking to the future for process launch events, using a way that looked to the past for events in the database works.