Description

Can we get a test scheduler algorithm that follows a greedy approach? Currently, the default scheduler follows a round robin-like approach to scheduler testing. But in some cases, we would want to saturate one node before moving to a new node. This is going to help us in scenarios where we have custom auto-scaler for the Selenium grid.

Have you considered any alternatives or workarounds?

No response