Repository: test-kitchen/test-kitchen

Issue #169: kitchen test --parallel never times out, never errors out, despite an error
Created: 2013-07-18T14:35:40Z
From celluloid.log:
E, [2013-07-18T10:25:39.228573 #22329] ERROR -- Celluloid: Kitchen::InstanceActor crashed!
Kitchen::ActionFailed: Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision ----
STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
STDERR: Your VM has become "inaccessible." Unfortunately, this is a critical error
with VirtualBox that Vagrant can not cleanly recover from. Please open VirtualBox
and clear out your inaccessible virtual machines or find a way to fix
them.
---- End output of vagrant up --no-provision ----
Ran vagrant up --no-provision returned 1]
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/shell_out.rb:73:in `rescue in run_command'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/shell_out.rb:61:in `run_command'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/driver/base.rb:146:in `run_command'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/kitchen-vagrant-0.10.0/lib/kitchen/driver/vagrant.rb:99:in `run'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/kitchen-vagrant-0.10.0/lib/kitchen/driver/vagrant.rb:48:in `create'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:249:in `public_send'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:249:in `block in perform_action'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:281:in `call'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:281:in `block in synchronize_or_call'
        <internal:prelude>:10:in `synchronize'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:279:in `synchronize_or_call'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@mytest/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:259:in `block in action'
        /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/benchmark.rb:280:in `measure'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:258:in `action'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:249:in `perform_action'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:228:in `create_action'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:222:in `block in transition_to'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:221:in `each'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:221:in `transition_to'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:143:in `verify'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:172:in `block in test'
        /var/lib/jenkins/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/benchmark.rb:280:in `measure'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/test-kitchen-1.0.0.alpha.7/lib/kitchen/instance.rb:168:in `test'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/legacy.rb:34:in `method_missing'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/calls.rb:25:in `public_send'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/calls.rb:25:in `public_send'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/calls.rb:25:in `dispatch'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/calls.rb:67:in `dispatch'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/actor.rb:326:in `block in handle_message'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/tasks.rb:42:in `block in initialize'
        /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p448@dd-agent-testing/gems/celluloid-0.14.1/lib/celluloid/tasks/task_fiber.rb:11:in `block in create'

Was running a suite of 6 different boxes, and after waiting a long time, a Ctrl+C exits, but doesn't clean up.

Duplicate issue #100: kitchen uses 100% CPU after a failure with the --parallel flag
Created: 2013-05-06T00:29:30Z
I've noticed that occasionally that if I start kitchen with the --parallel flag and one of the instances fails,  kitchen suddenly starts consuming 100% CPU.
Currently I have only seen this using the kitchen-openstack plugin and haven't yet tracked down whether the problem is in test-kitchen or the plugin.
> gem list celluloid

*** LOCAL GEMS ***

celluloid (0.13.0, 0.12.4)

> ruby -v
ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-darwin11.4.2]

Closing comment (2013-08-09T22:02:46Z): May be related to #169