On Oct 9, 2009, at 9:17 AM, Benoit Chesneau wrote:
On Fri, Oct 9, 2009 at 2:24 PM, Robert Dionne
<[email protected]> wrote:
fwiw, one thing these failed etaps all have in common is that they
start a
couchdb server
i retried by making sure any other couchdb was sown but still have
errors.
test/etap/110-replication-httpc...........FAILED before any test
output arrived
test/etap/111-replication-changes-feed....ok 5/13
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
test/etap/111-replication-changes-feed....dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 7-13
Failed 7/13 tests, 46.15% okay
test/etap/112-replication-missing-revs....ok 3/12
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
test/etap/112-replication-missing-revs....dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 5-12
Failed 8/12 tests, 33.33% okay
Failed Test Stat Wstat Total Fail List
of Failed
-------------------------------------------------------------------------------
test/etap/110-replication-httpc.t ?? ?? ??
test/etap/111-replication-changes-feed.t 1 256 13 14 7-13
test/etap/112-replication-missing-revs.t 1 256 12 16 5-12
Failed 3/25 test scripts. 21/331 subtests failed.
Files=25, Tests=331, 50 wallclock secs (13.54 cusr + 5.52 csys =
19.06 CPU)
Failed 3/25 test programs. 21/331 subtests failed.
make: *** [check] Error 1
about server launch wouldn't it be better to launch it on an available
port so it cannot conflict with anything?
good idea, will look into it.
- benoît
