Why do this cookbook forces to have a test/support dir for every cookbook? about minitest-handler-cookbook

[leifmadsen]

I'll give you that this is fairly ugly, but I think it was a change in Chef directly that causes the extra text output. I've run this on older versions of Chef and the output isn't as verbose. While it is verbose, there is no error or bug here.

[bryanwb]

it is more verbose cuz kallistec improved the output formatters

On Wed, Oct 10, 2012 at 2:39 PM, Leif Madsen [email protected]:

I'll give you that this is fairly ugly, but I think it was a change in
Chef directly that causes the extra text output. I've run this on older
versions of Chef and the output isn't as verbose. While it is verbose,
there is no error or bug here.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-9300075.

[leifmadsen]

It's certainly nice when you're wondering why your tests aren't triggering :) Seems like this can be closed as "not a bug" though.

[millisami]

Does it ignore the failure and the run will continue?
Coz I've tried couple of times before posting this here and it was halting the run saying with exist code non-zero the chef run just stops!

[bryanwb]

wow, it should just continue, that is why ignore_failure true is set

r u sure you aren't getting a non-zero error due to something else?

On Wed, Oct 10, 2012 at 8:18 PM, millisami [email protected] wrote:

Does it ignore the failure and the run will continue?
Coz I've tried couple of times before posting this here and it was halting
the run saying with exist code non-zero the chef run just stops!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-9313685.

[leifmadsen]

That's what I've always seen as well. It doesn't actually error out or cause any ill effects.

[bryanwb]

hey guys, am closing this as I can't replicate it