aglinxinyuan commented on issue #5549: URL: https://github.com/apache/texera/issues/5549#issuecomment-4644480033
Closing — while drafting the spec I discovered the existing cross-cutting `DeployStrategiesSpec.scala` in the same package already covers all three concrete strategies (`OneOnEach`, `RoundRobinDeployment`, `RandomDeployment`) including factory freshness, exhaustion, empty-array handling, single-element coverage, cyclic wrap-around, and membership semantics. Per the project's spec-filename convention, the cross-cutting spec is the right shape for this cross-class contract; opening parallel `<ClassName>Spec.scala` files would be the duplicate-spec failure mode the convention is designed to prevent. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
