>When I roll this 0.2 RC for Gora and if we release, all Nutchgora tests NEED to remain with Gora version 0.1.1-incubating as gora-sql jar is currently out of action pending an upgrade... I agree with this.
About the TestAPI, I just commented it out. That makes it very easy to revert, if one wishes to fix it (or when replaced by new implementation). It's just that it does not make any sense that when I run the test it only works some of the times. (Running the test twice in a row can make it succeed one time and fail the other one.) If anyone disagrees with this commit, please let me know. On Sun, Apr 8, 2012 at 6:29 PM, Lewis John Mcgibbney < lewis.mcgibb...@gmail.com> wrote: > When I roll this 0.2 RC for Gora and if we release, all Nutchgora tests > NEED to remain with Gora version 0.1.1-incubating as gora-sql jar is > currently out of action pending an upgrade... > > This is really interesting now. Even though the test passed, we still have > a horrible stack trace in the log output for this test. Indicating that > regardless of whether the build is 'healthy' this test is still not up to > scratch. Whereas before the build failed on testJobsAPI, it now passes but > the same stack traces are present. > > I've been over at hsql lists to see if there is any further configuration > we can add to reduce the likelihood of this happening as it seems to be > rather unpredictable. I'm awaiting feedback so it is entirely up to you if > you wish to disable testJobsAPI for the time being! I have no objection, > however it is obviously something we need to address. > > > On Sun, Apr 8, 2012 at 5:19 PM, Ferdy Galema <ferdy.gal...@kalooga.com>wrote: > >> Can't we just comment this test out? I really think this is the best >> solution for now as this test is just flapping for no apparent reason. Also >> I'm working on an API alternative (still in early phase) that will probably >> supersede the current implementation. >> >> +1 for commenting out. >> >> >
