On 2 Jun 2011, at 15:13, Paul Davis wrote: > On Thu, Jun 2, 2011 at 8:44 AM, Noah Slater <nsla...@apache.org> wrote: >> >> On 2 Jun 2011, at 09:38, Dave Cottlehuber wrote: >> >>> @nslater when "it hangs" is there anything of note happening in the >>> erlang logs/shell ? Throw us a bone! >> >> Nope, nothing. >> >> > If Chrome passed fine I'm guessing the error is in the browser.
I've seen this in the past occasionally, where the test suite does a _restart and then waits forever for CouchDB to come back. The Erlang console will show the regular startup procedure output, but then it just waits there for requests. I have verified that it actually *does* accept requests when it is in this state. Maybe it is the "wait for restart" routine that has a bug or triggers one inside Firefox. From the log: ... [info] [<0.2219.0>] 127.0.0.1 - - 'POST' /_restart 200 # _restart [info] [<0.2202.0>] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.0 (LogLevel=info) is starting. # startup logs Apache CouchDB has started. Time to relax. # cnt'd [info] [<0.2274.0>] Apache CouchDB has started on http://127.0.0.1:5984/ # hangs here [info] [<0.2790.0>] 127.0.0.1 - - 'GET' / 200 # verified that CouchDB accepts requests FWIW, this is the delayed_commits test. Cheers Jan --
