Found the culprit. It was RubyAMF.
We've emailed them about it.
In the meantime, for anyone else who might encounter this problem,
changing line 188 of controller_example_group from:
super(options, deprecated_status, &block)
to:
super(options, &block)
Makes al
Ok, I've ditched externals and switched to piston... wiped out all
the plugins and reinstalled them...
And still I'm getting that error.
No one else is getting this?
Daniel
On 28 Nov 2007, at 14:49 28 Nov 2007, David Chelimsky wrote:
> On Nov 28, 2007 8:44 AM, Daniel Tenner <[EMAIL PROTECTED
On Nov 28, 2007 8:44 AM, Daniel Tenner <[EMAIL PROTECTED]> wrote:
> 8228 and 2997! :-(
>
> Dang.. what else could it be? It looks like basically, "render" is
> what's broken... all the pages with redirect_to are working fine in
> the specs. When I take one of the broken actions and make it
> redire
8228 and 2997! :-(
Dang.. what else could it be? It looks like basically, "render" is
what's broken... all the pages with redirect_to are working fine in
the specs. When I take one of the broken actions and make it
redirect_to instead of rendering, the number of failures goes down,
and the
To avoid this sort of issue, I recommend using piston. With piston you can
check in revision combinations that actually work in your source tree
without using svn externals.
Stefan
2007/11/28, Daniel Tenner <[EMAIL PROTECTED]>:
>
> Hi all,
>
> Not sure if I'm the only one with this problem...
>
>
On Nov 28, 2007 8:29 AM, Daniel Tenner <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Not sure if I'm the only one with this problem...
>
> We're on edge for both rails and rspec, and i just did an update...
> Some apparently innocuous rails stuff was updated, and then half my
> specs broke due to an err
Hi all,
Not sure if I'm the only one with this problem...
We're on edge for both rails and rspec, and i just did an update...
Some apparently innocuous rails stuff was updated, and then half my
specs broke due to an error in rspec_on_rails:
ArgumentError in 'UserController without logged in u
