Re: Problems blocking 1.2.0 release

On Feb 7, 2012, at 12:50 , Noah Slater wrote: > On Mon, Feb 6, 2012 at 7:04 PM, Jan Lehnardt wrote: >> >> I'd suggest this looks like we are not using mochiweb.app.src at all >> and we could either delete it or keep to keep file-parity with upstream. >> >> (file-parity interlude, I'd prefer to

Re: Problems blocking 1.2.0 release

On Mon, Feb 6, 2012 at 7:04 PM, Jan Lehnardt wrote: > > I'd suggest this looks like we are not using mochiweb.app.src at all > and we could either delete it or keep to keep file-parity with upstream. > > (file-parity interlude, I'd prefer to keep upstream directories in as > much of the original

Re: Problems blocking 1.2.0 release

On Feb 6, 2012, at 20:04 , Jan Lehnardt wrote: > > On Feb 4, 2012, at 02:43 , Paul Davis wrote: > >> Doing some traveling but quick thoughts inline: >> >> On Fri, Feb 3, 2012 at 6:29 PM, Noah Slater wrote: >>> Hello, >>> >>> I have a 1.2.0 release ready to go, but there are a few problems th

Re: Problems blocking 1.2.0 release

On Feb 4, 2012, at 02:43 , Paul Davis wrote: > Doing some traveling but quick thoughts inline: > > On Fri, Feb 3, 2012 at 6:29 PM, Noah Slater wrote: >> Hello, >> >> I have a 1.2.0 release ready to go, but there are a few problems that need >> fixing before I am prepared to ship. >> >> Compar

Re: Problems blocking 1.2.0 release

Can anyone else weigh on this please? Specifically, the code. The documentation needs to be worked in to NOTICE. On Sat, Feb 4, 2012 at 1:43 AM, Paul Davis wrote: > Doing some traveling but quick thoughts inline: > > On Fri, Feb 3, 2012 at 6:29 PM, Noah Slater wrote: > > Hello, > > > > I have a

Re: Problems blocking 1.2.0 release

Doing some traveling but quick thoughts inline: On Fri, Feb 3, 2012 at 6:29 PM, Noah Slater wrote: > Hello, > > I have a 1.2.0 release ready to go, but there are a few problems that need > fixing before I am prepared to ship. > > Comparing our source to the release artefact, I get: > > Only in 1.

Problems blocking 1.2.0 release

Hello, I have a 1.2.0 release ready to go, but there are a few problems that need fixing before I am prepared to ship. Comparing our source to the release artefact, I get: Only in 1.2.0/src/mochiweb: mochiweb.app.src > Only in 1.2.0/src/mochiweb: mochiweb_request_tests.erl > Only in apache-couch

Re: Test suite problems blocking 1.2.0 release

Must've got much more noisy since last release! :) On Thu, Jan 26, 2012 at 11:52 AM, Jan Lehnardt wrote: > > On Jan 25, 2012, at 17:39 , Noah Slater wrote: > > > Seems to run fine, in the browser, once I've disabled the cache. > > > > Is it normal for the start of the log to look like this: > >

Re: Test suite problems blocking 1.2.0 release

On Jan 25, 2012, at 17:39 , Noah Slater wrote: > Seems to run fine, in the browser, once I've disabled the cache. > > Is it normal for the start of the log to look like this: Yes, the rest of the log looks legit. The crashes you are seeing are normal operations when we test restarting component

Re: Test suite problems blocking 1.2.0 release

You can turn off the cache, like Dave said. There's at least one test (in attachment_names, I think) that asserts a 304 status code, but it uses the If-None-Match header. Definitely the "lorem" error is from not clearing the cache before you run, though. The test suite should work with caching on,

Re: Test suite problems blocking 1.2.0 release

Yep, that's the same backtrace I saw when I poked which reminded me about the SSL stuff. Though, compiling an older SSL library vs. patching Erlang seems like the wrong way round to fix this. I wonder how hard it'd be to patch the NIF. On Wed, Jan 25, 2012 at 11:29 AM, Filipe David Manana wrote:

Re: Test suite problems blocking 1.2.0 release

On Wed, Jan 25, 2012 at 5:15 PM, Paul Davis wrote: > I've been seeing these segfaults as well. I looked at one and saw that > it was down in the SSL library which Filipe has reported issues with > on OS X 10.7 and Erlang. I forgot to ping him and ask if he had a > resolution yet though. With OTP

Re: Test suite problems blocking 1.2.0 release

I've been seeing these segfaults as well. I looked at one and saw that it was down in the SSL library which Filipe has reported issues with on OS X 10.7 and Erlang. I forgot to ping him and ask if he had a resolution yet though. Also it does appear to be related to init:restart() which we only use

Re: Test suite problems blocking 1.2.0 release

Seems to run fine, in the browser, once I've disabled the cache. Is it normal for the start of the log to look like this: Noahs-MacBook-Air:couchdb nslater$ /tmp/couchdb/bin/couchdb Apache CouchDB 1.2.0a-c7765f6-git (LogLevel=info) is starting. Apache CouchDB has started. Time to relax. [info] [<

Re: Test suite problems blocking 1.2.0 release

Getting more errors: [error] [<0.1183.0>] {error_report,<0.30.0>, {<0.1183.0>,crash_report, [[{initial_call, {couch_view_group,init,['Argument__1']}}, {pid,<0.1183.0>},

Re: Test suite problems blocking 1.2.0 release

I keep getting this: =ERROR REPORT 25-Jan-2012::16:00:50 === ** Generic server <0.442.0> terminating ** Last message in was {'EXIT',<0.369.0>,killed} ** When Server state == {db,<0.442.0>,<0.443.0>,nil,<<"1327507250852653">>, <0.444.0>,<0.440.0>,<0.446.0>,

Re: Test suite problems blocking 1.2.0 release

On 25 January 2012 16:01, Dave Cottlehuber wrote: > Noah try this: This time without small greasy-fingered helpers: turn on Private Browsing open about:config search for cache set network.http.use-cache = false set browser.cache.disk.enable = false And re-try tests. This should eliminate most of

Re: Test suite problems blocking 1.2.0 release

Noah try this: turn on Private Browsing open about:config search for cache set network.http.use-cache = false set On 25 January 2012 14:28, Noah Slater wrote: > Hey, > > Getting unpredictable failures with the test suite. Mac OS X, Firefox, > latest versions of both. > > attachments > error > 225

Test suite problems blocking 1.2.0 release

Hey, Getting unpredictable failures with the test suite. Mac OS X, Firefox, latest versions of both. attachments error 225ms Run with debugger 1. *Assertion failed:* xhr.responseText == lorem 2. *Exception raised:* {