-
Notifications
You must be signed in to change notification settings - Fork 17
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
Convergence fails with invalid character error #2
Comments
I get the same, with a slightly modified Guardfile, with the character "\xE2" |
Am having the same issue. Tried everything including grep all the files for the character and changing the encoding in the terminal but nothing works. |
I have had similar problems in the past, and was able to "resolve" them by nuking the Berkshelf caches completely (from ~/.berkshelf, everything except config.json). I probably could have resolved being more selective, but the problem was metadata (or a Berksfile) in one of the cached cookbooks. |
@buysse: I ran into this problem today and your solution worked for me ;) |
+1 to @buysse's workaround |
-1 to @buysse's workaround from my side. Even on a vanilla system, right after running running |
So the problem here is that Mixlib::ShellOut (at least on my machine) seems to be resetting the
everything works fine. |
BTW, the key change there is the explicit setting of |
Looks like this never closed when #5 merged! Closing out. |
With Guard running, and this Guardfile setup:
I get this failure when I modify one of the files that should trigger a
kitchen verify
:I can, however, after guard-kitchen has created the VMs for me, run
kitchen verify all -p
myself without any issue, so I don't believe the issue lies with Test Kitchen or any of my configuration.The text was updated successfully, but these errors were encountered: