On Tue, Apr 22, 2014 at 11:23 AM, Bryan Larsen <[email protected]> wrote:
> On Mon, Apr 21, 2014 at 7:23 PM, Michael DeHaan <[email protected]> > wrote: > > If you would ever like to report a crash, including the "result" of the >> crash is >> > needed to understand the context. >> Can you please paste the result you are receiving? >> > > I'm not sure why you want the backtrace; it's already fixed in 1.6 by > https://github.com/ansible/ansible/commit/2a976a. I've attached the > backtrace at the end of this email. > It's entirely because you send an email reporting a crash :) > > The actual crash is not my concern. > Should have probably indicated that in the first email :) > There are several different ways that you can crash ansible on skipped > roles. Another way to do it is via > > with_sequence: start=1 end={{ numFoo }} > > where numFoo is 0. That obviously should be an error when the task is > run. What is surprising that ansible still crashes with "can't count > backwards" even if you tell it to skip the role containing the task: > Conditionals are applied per loop step, not before the loop is evaluated. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxNbrj1k-XdgKMEM6QSsF%3DDxZPGx9nCpC5XaCdWLnLLeQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
