Skip to content
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

Tests are not executing on windows during Chef-Client run #72

Open
vinyar opened this issue Oct 31, 2013 · 2 comments
Open

Tests are not executing on windows during Chef-Client run #72

vinyar opened this issue Oct 31, 2013 · 2 comments

Comments

@vinyar
Copy link
Contributor

vinyar commented Oct 31, 2013

When a known good recipe is loaded with Chef-Handler on windows, tests are not being executed during a Chef-client run. However, the same set of recipes works fine as Chef-Solo.

Details:
Chef version 11.8
minitest-handler 1.1.2
chef_handler 1.1.4
chef-client 3.1.0

Runlist:
recipe[chef-client::delete_validation]
recipe[minitest-handler]

Results in Chef-Client:
- execute the ruby block load tests
Chef Client finished, 16 resources updated

Results in Chef-Solo:
- execute the ruby block load tests←[0m
...

Running tests:

chef-client::delete_validation#test_0001_deletes the validation key file = 0.00 s ..
recipe::chef-client::delete_validation#test_0001_deletes the validation key file = 0.00 ..

Finished tests in 0.000000s, Inf tests/s, Inf assertions/s.
2 tests, 2 assertions, 0 failures, 0 errors, 0 skips
Chef Client finished, 5 resources updated←[0m

Expectation:
Chef-Client should find and execute the tests.

@dpetzel
Copy link
Contributor

dpetzel commented Dec 6, 2014

@vinyar Any chance you're using the minitest-handler cookbook for this? Sounds an aweful lot like btm/minitest-handler-cookbook#65

TLDR - Ensure the version of the cookbook is 1.3.2

@vinyar
Copy link
Contributor Author

vinyar commented Dec 17, 2014

@dpetzel thanks for the reply - definitely good to know. In the last year I've moved entirely to using chefspec/serverspec. I can't even remember filing this bug. It may not even be an issue any longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants