Skip to content

249 ensemble instances not all running concurrently#250

Merged
markcoletti merged 16 commits into
0.9.0-prereleasefrom
249-ensemble-instances-not-all-running-concurrently
Jun 19, 2026
Merged

249 ensemble instances not all running concurrently#250
markcoletti merged 16 commits into
0.9.0-prereleasefrom
249-ensemble-instances-not-all-running-concurrently

Conversation

@markcoletti

Copy link
Copy Markdown
  • Uses Client.map() instead of Client.submit() to send tasks
  • Fixed bug where we were blocking twice awaiting futures from ensemble tasks.
  • Tweaked handling of logfile and errfile parameters for launch() including adding of test harness

…then explicitly printed if logfile and errfile are not already provided. Also, since we want to capture stdout/stderr as text, we need to specify text=True for that to happen. We also log to the root logger so that forward_logging() (hopefully) works.
…unning-concurrently' into 249-ensemble-instances-not-all-running-concurrently
@markcoletti markcoletti self-assigned this Jun 19, 2026
@markcoletti markcoletti merged commit a52b4c0 into 0.9.0-prerelease Jun 19, 2026
0 of 13 checks passed
@markcoletti markcoletti deleted the 249-ensemble-instances-not-all-running-concurrently branch June 19, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant