Re: Re: JRuby on Rails

All true.  What I like to do, is just start deleting chunks of code that don't 
appear to be relevant (Naturally, you'll want to do this with a "special 
install of ruby, that you can easily restore).  Then run the failing code 
again. Binarily dividing the problem like this seems one of the fast ways to 
create a simple test case when you're not sure where the REAL problem is.

On Wednesday 22 February 2006 07:31 pm, Charles O Nutter wrote:
> This is certainly an acquired talent I can't say I've mastered yet.
> Digging down into any Ruby application can be a daunting task; with
> Rails, daunting doesn't do it justice. Rails code not only mutilates
> itself in various execution scenarios, it mutilates core Ruby
> functions with its own enhanced versions. Discovering where someting's
> failing becomes an excercise in pain.
>
> However, it does get easier with time. The stack dumps in JRuby are
> better now than they used to be and usually reflect where a problem
> actually happened. One can also quickly learn the key spots in the
> code to set breakpoints for specific sorts of failures; running
> script/generate in debug mode allowed me to pinpoint several failures
> deep, deep within Rails. And of course, knowledge of Rails code is a
> huge help...I'm sure in the course of getting this working we'll learn
> more about Rails than any of us ever wanted to. I know I've seen
> things noone should have to see, and we're just at the beginning of
> this adventure.
>
> On 2/22/06, David Corbin <dcorbin@xxxxxxxxxxxxxx> wrote:
> > Running the RoR tests is not a bad idea, but the problem is (I think)
> > that their "unit-tests" excercise hundreds of RoR methods (not to mention
> > all the core and stdlib things).   This is probably a quick way easy way
> > to find failures, but we still need to find out WHY it's failing.  In the
> > Rails code this is a LOT harder than in some other code.
> >
> > In a recent problem we ran across (not RoR related), there was one regex
> > deep inside REXML that was causing problems.  I had a very reliable test
> > that failed, but until we REALLY narrow the amount of Ruby code being
> > interpretted, we can't really fix it.
>
> --
> Charles Oliver Nutter @ headius.blogspot.com
> JRuby Developer @ jruby.sourceforge.net
> Application Architect @ www.ventera.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Jruby-user mailing list
> Jruby-user@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/jruby-user


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642