#1075: Test cases with specific number of processes --------------------------+------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: review Priority: major | Milestone: Component: Cactus | Version: Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by knarf):
I agree that we are able to request more processes through the queuing system than needed, and then run (most tests) with less and a few (that request more) using up to the requested amount. But that is not my point. Applying this patch as is would break the testsuite mechanism for cases that currently work, it would be a regression. Simfactory might be used to circumvent this a bit, but it also has to work without.
Let me suggest something else. What I believe is a problem is that with this patch Cactus will try "to be smart", overrides a users decision and might actually fail. What I believe the intention of the patch is that Cactus should run as many testsuites as possible, even if that means using different numbers of processes for different tests. So, why don't we add an option to the test system that, instead of specifying a fixed number of processes, specifies 'as many processes as needed, and if nothing is specified then use the default of 1 (which we should be able to change, and simfactory might actually do that). This would introduce one more option for the testsuite mechanism. It wouldn't break anything if this is not the default in Cactus, and it could be the default within simfactory because there we know whether a machine supports over-subscribing or not.