Can distributed testing use a pool of hosts that can be accessed on a 'first available' basis?
I'm currently using distributed testing (1 master with 3 slaves) using Jobs to determine which slave gets which project. The projects are essentially 'hard-coded' to a specific slave (Host). ...
Please increase the rating for the suggestion in the DB for me as well. I am in a similar situation where I have hosts sitting idle waiting for the longest task in the job to complete.