All, Firstly, thank you to everyone who took the time to vote on this artifact.
Unfortunately I'm voting -1 and aborting round one of this release. We've uncovered a bug serious enough that we would like a fix for it to ship with 1.1.0 (COUCHDB-885). The behavior at fault is not verified by any of our automated tests, which is why no one in this thread has seen it. This bug appears to have been present in all releases since 0.10.2 but is not present on trunk (0.11.x has a slightly different replicator to 0.10.x, and trunk has a whole new one). Round 2 will begin once we have fixed 885 and any related tickets. Thanks again! B. On 17 May 2011 18:27, Paul Davis <paul.joseph.da...@gmail.com> wrote: > On Tue, May 17, 2011 at 1:21 PM, Paul Davis <paul.joseph.da...@gmail.com> > wrote: >> On Tue, May 17, 2011 at 1:15 PM, Noah Slater <nsla...@apache.org> wrote: >>> I'm getting the following unit test failures: >>> >>> http://friendpaste.com/ZMbw7g2OxETvcAzEDDcGv >>> >> >> This is a known race condition. The problem is the test, not what's >> being tested. >> >>> I tried running CouchDB and got a segfault. >>> >> >> Can you reproduce it? Which test was running when it failed? If you >> can reproduce it, can you attach gdb to your couchdb process to get a >> stack trace of when it segfaults? >> >>> I'm on OS X, latest version, yada yada. >>> >>> Let me know if you need any more information. >>> >> > > I'm getting an error in Futon in Chrome in the replicator test: > > Assertion failed: dbB.open("30") !== null > > Also I had it fail once so that an admin was left configured which > cause every other test to fail. >
