search for: reset_all

We''ve just added rspec stories to our CruiseControl.rb build. When there''s a failing scenario we see the failure in the log output, but it doesn''t cause the CruiseControl build to fail. We''ve also just upgraded to the latest rspec version, 1.1.4, which fixes rspec bug 228, but the CC.rb build is still passing. Has anyone got failing rspec stories making

...;func = urlfetch_continue; + cmd->context = ufctx; + return FALSE; + } + return urlfetch_finish(ufctx); +} + +// RESETKEY command +static bool cmd_resetkey(struct client_command_context *cmd) +{ + const struct imap_arg *args; + const char *mailbox = NULL; + const char *mechanism = NULL; + bool reset_all = FALSE; + struct mail_storage *storage; + + /* [mailbox [mechanism]] */ + if (!client_read_args(cmd, 0, 0, &args)) + return FALSE; + + if (IMAP_ARG_TYPE_IS_STRING(args[0].type)) { + mailbox = imap_arg_string(&args[0]); + + /* mechanism name may be absent, empty, or "INTERNAL"...