Re: [gitorious] fixing tests in "next"

2013-07-04 Thread Christian Johansen
> Finally found it! When running through "bundler exec rake", the test > suite was running through rake_test_loader, which finds all the tests > and calls "Require" on each one. I modified this program to show which > specific test was causing the crash. It was > test/functional/searches_controller

Re: [gitorious] fixing tests in "next"

2013-07-04 Thread Ken Dreyer
On Fri, Jun 28, 2013 at 8:10 AM, Christian Johansen wrote: >>> There is also a problem related to the way that execute() gets called >>> on anonymous classes on Ruby 1.8.7. I tried to wrap my mind around the >>> use_case gem so I could understand how to fix it, but it is beyond me. >>> I've filed

Re: [gitorious] fixing tests in "next"

2013-06-28 Thread Christian Johansen
>> There is also a problem related to the way that execute() gets called >> on anonymous classes on Ruby 1.8.7. I tried to wrap my mind around the >> use_case gem so I could understand how to fix it, but it is beyond me. >> I've filed the details at https://issues.gitorious.org/issues/177 > > I'm l

Re: [gitorious] fixing tests in "next"

2013-06-28 Thread Marius Mårnes Mathiesen
Ken Dreyer writes: > I recently investigated some test suite failures on the "next" branch. ♥ > For Fedora 19 (Ruby 2.0.0), there's a really simple adjustment that is > needed. The details are at > https://gitorious.org/gitorious/mainline/merge_requests/235 Great - thanks! I just merged this,

[gitorious] fixing tests in "next"

2013-06-27 Thread Ken Dreyer
I recently investigated some test suite failures on the "next" branch. For Fedora 19 (Ruby 2.0.0), there's a really simple adjustment that is needed. The details are at https://gitorious.org/gitorious/mainline/merge_requests/235 For CentOS 6 (Ruby 1.8.7), the failures are more complex. The "refut