[chef] Re: Re: Chefspec Errno::ENOMEM

["Stewart, Curtis" < >]

Thanks Steven.

It appears that rspec/chefspec is taking up all my memory.  If anyone is aware of similar issues and found better versions to work with, could you list your environment?

Near the beginning of my tests, only ~ 20% of my memory if being allocated to rspec.  Near the end (about 14 min later), nearly 65% is used (top output below).

top output:

28985 jenkins   20   0 1438m 1.3g 5196 R  100 65.1  14:35.13 ruby

Here’s my current environment:

  * chefspec (3.1.4)

  * rspec (2.14.1)

  * rspec-core (2.14.7)

  * rspec-expectations (2.14.5)

  * rspec-mocks (2.14.5)

ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]

rvm 1.25.17 (stable)

Thanks,

Curtis

On Feb 11, 2014, at 10:16 AM, Steven De Coeyer < "> > wrote:

Curtis

It looks like your server is maxed out of free memory. It can no longer allocate new memory to new processes.
You’ll have to upgrade your server memory or find out what’s taking up all of the memory and do something about that.

Kind regards,
Steven

On 11 Feb 2014, at 16:58, Stewart, Curtis < "> > wrote:

On a handful of recipes, we’re getting the following errors and cannot seem to avoid them.  The pattern appears to be with any `Mixlib::ShellOut` commands.

Working in a chef-repo.

chef-client v11.8.0
chefspec v3.1.4

We’re currently running specs on our entire repo through a Jenkins server.  

recipe code:

cmd1 = Mixlib::ShellOut.new("s3cmd info #{node[‘app']['s3_source']} | grep MD5 | awk '{print $3}'").run_command

error:

Errno::ENOMEM:
      Cannot allocate memory - fork(2)



Thanks,
Curtis