Actions
action #7982
closedmulti machine test that actually involves different machines
Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2015-06-22
Due date:
% Done:
0%
Estimated time:
Description
multi machine scheduling currently assumes that all linked jobs run on the same machine. There should be a way to have different machines talk to each other. Maybe with a syntax like like PARALLEL_WITH="test@machine"?
Actions