-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
service().must_be_running doesn't properly work on CentOS #66
Comments
I believe there are two issues here.
|
@stevendanna Is there a way to tell minitest to use a different provider, if you know for example that its an upstart service instead of lsbinit or whatever? |
@ppgengler We had this issue with vmware tools which uses upstart on RH6 and init on RH5.
|
@ppgengler An alternative to something like superted mentioned would be something like: https://github.com/opscode-cookbooks/chef-client/pull/115/files |
^ Definitely a cleaner method. |
That's cool, although I'll admit I was hoping for something on the minitest-chef-handler side like:
That did that work for me; perhaps even took symbols like |
👍 @ppgengler that syntax looks ideal to me |
I have the following assertion test in
test/cookbooks/cubrid_test/files/default/tests/minitest/default_test.rb
file.Running it CentOS 6.4 x64 Vagrant box via Test Kitchen returned the following failure:
If I login to this CentOS Vagrant box, I can confirm that the service is running:
Running Kitchen test on Ubuntu 10+ Vagrant boxes, passes all tests.
The text was updated successfully, but these errors were encountered: