[Swift-devel] Intentional change to behavior of high/lowOverAllocation parameter?

[Mihael Hategan]

On Wed, 2011-09-14 at 17:57 -0500, Michael Wilde wrote:
> Mihael,
> 
> For quite a while now I have been telling people to set the coaster parameters lowOverAllocation and highOverAllocation to 100 to force coasters to set the time allocation of every block to maxTime. (This was based on your advice around the time we started running on Beagle, to enable the user to force a specific and constant PBS job walltime).
> 
> Cog rev 3225 seems to have introduced a change that insists that these two parameters have a value < 1.0:
> +        checkLessThan("lowOverallocation", 1);
> +        checkLessThan("highOverallocation", 1);

Whoops! I clearly meant GreaterThan. I'm not sure why my computer didn't
commit what I wanted instead of what I wrote.

r3273.