The Jenkins framework may not be properly declining offers, nor merging new offers with other outstanding offers from the same slave. For example, if two smaller (455MB) tasks on the same slave complete in sequence, your Jenkins framework could get two separate 455MB offers, but you could merge them and launch a single task that uses 910MB.
On Sun, Feb 1, 2015 at 11:50 PM, Dick Davies <d...@hellooperator.net> wrote: > The offer is only for 455 Mb of RAM. You can check that in the slave UI, > but it looks like you have other tasks running that are using some of that > 1863Mb. > > On 2 February 2015 at 05:11, Hepple, Robert <rhep...@tnsi.com> wrote: > > > Yeah but ... the slave is reporting 1863Mb RAM and 2 CPUS - so how come > > that is rejected by jenkins which is asking for the default 0.1 cpu and > > 512Mb RAM??? > > > > > > Thanks > > > > > > Bob >
