couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1762) Improve javascript test suite
Date Fri, 05 Apr 2013 20:07:18 GMT


Alexander Shorin commented on COUCHDB-1762:

`make check` output log:

In my case, during testing 1.3.0 RC, I'd failed test 49 rev_stemming and server crush after
72 one:

Reason: false
not ok 49 rev_stemming
Trace back (most recent call first):
46: /home/kxepal/temp/apache-couchdb-1.3.0/test/javascript/cli_runner.js
29: /home/kxepal/temp/apache-couchdb-1.3.0/share/www/script/test/rev_stemming.js
53: /home/kxepal/temp/apache-couchdb-1.3.0/test/javascript/cli_runner.js
runTestConsole(49,"rev_stemming",(function (debug) {var db = new Couch
72: /home/kxepal/temp/apache-couchdb-1.3.0/test/javascript/cli_runner.js
85: /home/kxepal/temp/apache-couchdb-1.3.0/test/javascript/cli_runner.js
ok 71 view_update_seq
Test failures: 1
ok 72 view_xml
Apache CouchDB crashed, restarting in 1 second.
Apache CouchDB has been shutdown.
make[1]: *** [check-js] Error 2
make[1]: Leaving directory

Now this looks fixed, but etap test 077-couch-db-fast-db-delete-create.t fails by mysterious
reason. I'll try to check what's happened and make an update if I find something.
> Improve javascript test suite
> -----------------------------
>                 Key: COUCHDB-1762
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Wendall Cada
>            Assignee: Wendall Cada
> In 1.3.0, there is a new part of the test suite to run the javascript tests from the
command line. Some people are experiencing intermittent failures on different hardware/OS
configurations. Mostly, tests hanging or timing out and failing. These are really hard to
troubleshoot, as they all pass just fine if run individually.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message