Fix for subjob spawning with FIFOs #13824
Merged
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.
When running jobs spawning with GeneratorFileOrCmd it could happen that the subjob is still running after the FIFO has been deleted by the destructor. This was not a problem before the destructors Fix, but it is now, especially in situations in which the number of events to be generated by the subgenerator exceeds the actual needed number for the o2-sim generation (such as hyperloop configurations). This fix implements a different spawning mechanism using fork() and allows the destructor to kill the subjobs via their PIDs.