MSGEN integration - consider concurrent execution limits
Open
cloud/azure
priority/low
- Dominant language
- Java
- Stars
- 163
- Forks
- 65
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 29
Description
MSGEN limits the number of concurrent executions to 20 (default value).
We shall consider this when scheduling multi-sample runs from the Cloud Pipeline.
We shall verify MSGEN behavior when oversubscription occurs. Can we just try to submit everything, and handle error messages to keep a sample(s) in the queue? Or a more fancy logic is required.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.