On Wed, Oct 19, 2011 at 18:12, Paul Davis <[email protected]>wrote:
> On Wed, Oct 19, 2011 at 5:00 PM, Sam Bisbee <[email protected]> wrote: > > On Wed, Oct 19, 2011 at 3:52 PM, Jan Lehnardt <[email protected]> wrote: > >> > >> On Oct 19, 2011, at 21:25 , Sam Bisbee wrote: > >> > >>> Yeah, it looks like it's just an unstable test. Which makes me wonder > >>> why we even have it or include it in the release process. > >> > >> It is only unstable in certain environments and we are constantly > improving all tests to be more stable in all environments, but the browser > world is harsh :) > > > > I'm all for improvement. :) But is this improvement being tracked > > anywhere, JIRA or otherwise? And if not, then could it be? I'm sure > > that folks (self included) would be willing to pitch in if we knew > > what had to be done. > > > > There was a thread about splitting Futon tests out and making them > proper CLI tests that are run as part of `make check` and become > actual release blockers. I have often and loudly voiced my support of > this approach. I refer you to the number of varying reports for 1.1.1 > with various browsers as Exhibit A in favor of this switch. > +1 I opened an issue and assigned it to me: https://issues.apache.org/jira/browse/COUCHDB-1312 -Randall
