[chef] Re: Re: Trouble with test-kitchen


Chronological Thread 
  • From: David Petzel < >
  • To:
  • Subject: [chef] Re: Re: Trouble with test-kitchen
  • Date: Sat, 18 Aug 2012 09:17:53 -0400

hmmm. OK, I mentioned I'm a ruby noob, so bundler and creating Gemfile will be new to me. I'll need to get up to speed on both, and give this a shot.

Out of curiosity, why is veewee even loaded? I'm simply running the tests against existing baseboxes. As I understand veewee is simply for automatting the creation of new baseboxes, If we are not creating a new one, does veewee really need to load? Or is this just a byproduct of way its included (Again please bear with my ruby 'noobness', if this is a dumb question)

On Fri, Aug 17, 2012 at 10:58 PM, AJ Christensen < " target="_blank"> > wrote:
Oh.. uhh.. just re-read this..

Use bundler and setup a Gemfile that has 'test-kitchen' in it, then
you can bundle install --binstubs and use bin/test-kitchen or bundle
exec like I said before, i.e.;

https://github.com/fujin/chef-discovery/blob/develop/Gemfile#L4

You should get something like this:

haxstation :: ~/dev/chef-discovery ?develop? ? bundle exec kitchen
test

                                                            1 ?
checking chef-discovery
Running syntax check on chef-discovery
Validating ruby files
Validating templates

Assembling required cookbooks at
[/home/aj/dev/chef-discovery/test/kitchen/.kitchen/cookbooks].
[centos-5.8] Box opscode-centos-5.8 was not found. Fetching box from
specified URL...

Cheers,
> I was attempting to get test-kitchen up and running on my ubuntu  machine
> tonight for a cookbook I'm working on, but I can't seem to get past the issue
> below.
>
> I'm pretty much a ruby noob, so its very possible I'm doing something wrong,
> but I just followed the steps in the quick start guide first
>
> Then I noticed I was getting some issues from foodcritic and FC007
> (https://github.com/acrmp/foodcritic/issues/44) so I ran a gem install
> foodcritic so that it would update foodcritic. I did take not that thor was not
> a dependency that was updated when I did that.
>
> From there I re-run kitchen test and get the following.
>
> Any idea?
>
> Assembling required cookbooks at ..........
>
> /usr/lib/ruby/1.9.1/rubygems/specification.rb:1615:in `raise_if_conflicts':
> Unable to activate veewee-0.2.3, because thor-0.16.0 conflicts with thor (~>
> 0.14.6) (Gem::LoadError)
>         from /usr/lib/ruby/1.9.1/rubygems/specification.rb:738:in `activate'
>         from /usr/lib/ruby/1.9.1/rubygems.rb:209:in `rescue in try_activate'
>         from /usr/lib/ruby/1.9.1/rubygems.rb:206:in `try_activate'
>         from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:58:in `rescue in
> require'
>         from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require'
>         from
> /home/user/.vagrant.d/gems/gems/veewee-0.2.3/lib/vagrant_init.rb:5:in `rescue
> in <top (required)>'
>         from
> /home/user/.vagrant.d/gems/gems/veewee-0.2.3/lib/vagrant_init.rb:1:in `<top
> (required)>'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:68:in
> `load'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:68:in
> `block (2 levels) in load!'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:42:in
> `each'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:42:in
> `block in load!'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:37:in
> `each'
>         from /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/plugin.rb:37:in
> `load!'
>         from
> /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:514:in
> `load_plugins'
>         from
> /var/lib/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:97:in
> `initialize'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/runner/vagrant.rb:78:in
> `new'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/runner/vagrant.rb:78:in
> `vagrant_env'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/runner/vagrant.rb:32:in
> `provision'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/cli/test.rb:37:in
> `block in run'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/project/base.rb:48:in
> `block in each_build'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/project/base.rb:47:in
> `each'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/project/base.rb:47:in
> `each_build'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/project/cookbook.rb:77:in
> `each_build'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/cli/test.rb:31:in
> `run'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/cli.rb:107:in
> `run'
>         from
> /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/lib/test-kitchen/cli.rb:71:in `run'
>         from /var/lib/gems/1.9.1/gems/test-kitchen-0.5.0/bin/kitchen:7:in `<top
> (required)>'
>         from /usr/local/bin/kitchen:19:in `load'
>         from /usr/local/bin/kitchen:19:in `<main>'




Archive powered by MHonArc 2.6.16.

§