[chef] Re: Possible problem with parallel testing with test-kitchen

["Scott M. Likens" < >]

Dan,

Unfortunately yes.  I was able to reduce it to 1 GET (installation of bats, minitest is installed via rubygems so it does not hit github) by modifying neutering the installation script at https://github.com/opscode/kb/blob/go/install to https://gist.github.com/damm/c7e89264f3130b2c62fc and modify lib/kitchen/busser.rb to point to a different INSTALL_URL.  With that small change this reduces the problem greatly.

I imagine there are many ways to reduce this pain I'm just not sure of the quickest and sanest path.

If there's anyway I can help let me know

Thanks!

On Mar 11, 2013, at 9:50 PM, Daniel DeLeo < "> > wrote:

Do conditional GETs or HEAD requests count against the limit?

-- 

Daniel DeLeo

On Sunday, March 10, 2013 at 3:58 PM, Scott M. Likens wrote:

Hi,

We've been having fun using the lxc driver for testing with test-kitchen (which makes testing really fast!).  Unfortunately I forgot that GitHub has rate limiting imposed now.  (60 requests were used up in less than 15 minutes (in part because LXC is so fast at creating and destroying guests and booting new guests ))

:~/git/haproxy_lwrp# curl https://api.github.com/rate_limit -u "damm"

Enter host password for user 'damm':

{

  "rate": {

    "limit": 5000,

    "remaining": 5000

  }

}

:~/git/haproxy_lwrp# curl https://api.github.com/rate_limit

{

  "rate": {

    "limit": 60,

    "remaining": 60

  }

}

I believe a few api requests occur in https://github.com/opscode/test-kitchen/blob/1.0/lib/kitchen/busser.rb#L100

I don't think the right answer is 'can we ship Kitchen Busser with Omnibus a/k/a Chef-full'. 

Could we move https://raw.github.com/opscode/kb/go to opscode.com like we do with the full installer? curl -L https://www.opscode.com/chef/kb.sh? with that we could reduce the github api requests.  

the basic error seen when getting this can be found https://gist.github.com/damm/5130887

P.S. I can create an issue for this, I just wanted to start a conversation about it and get a general idea of where we wanted to steer this before hand.

Thanks!

!DSPAM:513eb44a175911804284693!