Accidentally included half an idea on trying to make sure that the CouchDB process spawned by the JS CLI tests exited.
This test deletes a database and then tries to go and write to it without ensuring that it exists. This is just a race with the auth cache code trying to recreate its own database. This addition just makes sure it exists by trying to create it and ignoring any 412 errors if the auth cache won the race.
This should fix the random failures for the 'expected "25" got "31" error message that pops up occasionally. If my hunch is correct when we remove the two docs from the source db its possible to get the writes on the target out of order depending on a race condition. This just sleeps a bit in between the deletions to try and reduce that possibility. I haven't spotted this error after applying this patch.
Because the task status is updated only if the time elapsed since the last task status update is greater than some treshold, the value of the changes_done property might be smaller than TotalChanges. Closes COUCHDB-1451
- correct Firefox test suite usage notes
It's not clear if this is etap, escript, prove, or couchdb. This needs further investigation. Jira-1424