Skip to content

fix: correct scheduling of ref data requests when concurrency > 1 - #903

Merged
chrispcampbell merged 1 commit into
mainfrom
chris/902-suite-runner-ref-data
Aug 27, 2026
Merged

fix: correct scheduling of ref data requests when concurrency > 1#903
chrispcampbell merged 1 commit into
mainfrom
chris/902-suite-runner-ref-data

Conversation

@chrispcampbell

Copy link
Copy Markdown
Contributor

Fixes #902

See issue for details. This only affects the model-check packages and only in the less common case where non-default concurrency settings are used.

AI disclosure: I guided Claude Code (Opus 5) to plan and implement the changes, and then I reviewed and refined the changes.

@chrispcampbell
chrispcampbell merged commit f821c42 into main Aug 27, 2026
6 checks passed
@chrispcampbell
chrispcampbell deleted the chris/902-suite-runner-ref-data branch August 27, 2026 19:50
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.

Check suite runner has timing issue when concurrency > 1 and test relies on ref data

1 participant