Yes, errors during the test suite aren't necessarily bugs. Many of the
tests forcibly restart the database server, errors that may occur
during these restarts can be ignored.
If you are getting the errors in production though, that's likely a bug.
-Damien
On Jan 23, 2009, at 11:44 AM, Chris Anderson wrote:
I've been seein that exception as well, but only occasionally. My
first guess is that it is related to creating and destroying the
test suite db in such a short time span.
Sent from my iPhone
On Jan 23, 2009, at 2:20 AM, Robert Dionne <[email protected]>
wrote:
This is very cool, I'll check it out.
After a build with yesterday's changes I started seeing these
exceptions again: http://gist.github.com/50826
This was fixed (#213) a few days ago. I lowered max_open_databases
on my machine to 50 and it still occurs. It only occurs once when
running the tests from Futon, which all pass. However when running
the tests standalone from the runner script, you'll see two or
three. Running these requires the patch I submitted to couch_js.c
I'll try to run this down (no pun intended :)
Bob
On Jan 22, 2009, at 11:18 PM, Damien Katz wrote:
I just checked in code to allow the checking of the status of long
running tasks, like view indexes and compaction.
During a long view build or compaction, if you want to see the
status of what's happening, simply GET _active_tasks and you'll
get back a list of JSON objects describing the currently running
tasks.
Example results while 2 tasks are running:
[{"type":"Database Compaction","task":"speed","status":"Copied
10001 of 39001 changes (25%)","pid":"<0.78.0>"},
{"type":"View Group Indexer","task":"speed _design/
test","status":"Processed 0 of 39001 changes
(0%)","pid":"<0.91.0>"}]
We should probably add task tracking code for replication as well.
-Damien
