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.

Sign up for GitHub

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

Jump to bottom

unintuitive error message when kitchen driver specified in .kitchen.yml isn't found #80

Closed
juliandunn opened this issue Apr 12, 2013 · 1 comment
Closed

unintuitive error message when kitchen driver specified in .kitchen.yml isn't found #80

juliandunn opened this issue Apr 12, 2013 · 1 comment
Labels
Bug

Comments

@juliandunn
Copy link

I tried to use test-kitchen 1.0.0 alpha 4 with Vagrant 1.1 and got the following ugly message:

https://gist.github.com/juliandunn/f422b3f9ae824571cbb7

After some discussion with @jtimberman, we determined that I'd never installed the kitchen-vagrant driver that's specified in the bluepill cookbook's .kitchen.yml. This is not easily determined from the test-kitchen error output.
fnichol added a commit that referenced this issue Apr 20, 2013
@fnichol
Add a more helpful error message when a driver could not be loaded.
38c190d 
References #80
@jtimberman
Copy link
Contributor

Looks like 38c190d resolves this.

@test-kitchen test-kitchen locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jtimberman @juliandunn