Skip to content

Improve concurrency design #135

Description

@chlowell

There are a number of scenarios in which waza isn't as concurrent as it could be or appears it should be given configuration. For example, waza run --workers 6 ... on an eval suite having 3 tasks and 3 trigger tests gets only 3 concurrent sessions because all tasks complete before the first trigger test runs. My first thought is, how about a worker pool?

Metadata

Metadata

Labels

No labels
No labels

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions