Heya,
thanks all for chipping in with getting the JS test suite into shape!
I think we have a handle on it now, although there are few more curiosities
that it’d be nice to get some light on from the cluster experts here.
All of these are run on a -n 1 cluster.
1. reduce.js: Error: expected '
Hi all,
I guess the three parties last week plus 2day made a difference already -
branch 2876-js-tests starts filling and we got some bugs fixed, too. As I
see it, all replicator DB tests can be fixed more or less stereotypically.
I can pick this up Fri+ unless s/o else does it before me.
Off cou
Hi all,
got a little further at https://github.com/janl/couchdb/pull/3/files
This is it so far:
# for i in test/javascript/tests/a* test/javascript/tests/b*
test/javascript/tests/change*; dev/run -n 1 -q --with-admin-party-please
test/javascript/run $i; done
test/javascript/tests/all_docs.js
I’ve run the 1.x test suite against an -n1 cluster and it doesn’t improve things
significantly, although I haven’t looked at database deletes, as I’ve got these
covered for now.
So there is still some work that needs doing :)
Best
Jan
--
> On 12 Oct 2015, at 13:30, Dale Harvey wrote:
>
> Star
ok this is a short update of Jan's description for new folks starting with
fixing the tests (thank's in advance).
1. Check out https://github.com/janl/couchdb/tree/js-tests-on-2.0-wip
2. cd into the repo and `git checkout js-tests-on-2.0-wip`
3. run `make clean if this is not the first time you bu
> On 12 Oct 2015, at 13:33, Jan Lehnardt wrote:
>
> Oops, hits end too early.
>
>
> Okay -n 1 explains this
And again, butterfingers!
…-n 1 explains this.
I’m afraid this hides potential issues because we are testing a condition
that is, while definitely common (presumably), not necessarily
Oops, hits end too early.
Okay -n 1 explains this
> On 12 Oct 2015, at 13:32, Jan Lehnardt wrote:
>
>
>> On 12 Oct 2015, at 13:30, Dale Harvey wrote:
>>
>> Started with
>>
>> python dev/run -n 1 --with-admin-party-please &
>>
>> and export COUCH_HOST='http://127.0.0.1:15984'
>>
>>
>> On
> On 12 Oct 2015, at 13:30, Dale Harvey wrote:
>
> Started with
>
> python dev/run -n 1 --with-admin-party-please &
>
> and export COUCH_HOST='http://127.0.0.1:15984'
>
>
> On 12 October 2015 at 13:26, Jan Lehnardt wrote:
>
>>
>>> On 12 Oct 2015, at 13:15, Dale Harvey wrote:
>>>
-
Started with
python dev/run -n 1 --with-admin-party-please &
and export COUCH_HOST='http://127.0.0.1:15984'
On 12 October 2015 at 13:26, Jan Lehnardt wrote:
>
> > On 12 Oct 2015, at 13:15, Dale Harvey wrote:
> >
> >> - instead of fixed test db names like `test_suite_db` that are used in
> >
> On 12 Oct 2015, at 13:15, Dale Harvey wrote:
>
>> - instead of fixed test db names like `test_suite_db` that are used in
> almost every test,
>> we now generate a random database name for each test. The JS tests
> expected db
>> deletion to be synchronous, and that’s no longer the case in 2.0.
Ah, it looks I suck at instructions:
running make javascript starts the test cluster for you, with just
./test/javascript/run you have to run dev/run in another terminal first.
Best
Jan
--
> On 12 Oct 2015, at 13:19, Andy Wenk wrote:
>
> Hey Jan,
>
> I call it like this:
>
> ~/p/c/couchdb-j
Hey Jan,
I call it like this:
~/p/c/couchdb-js-tests git:js-tests-on-2.0-wip: ./test/javascript/run
test/javascript/tests/all_docs.js
FAIL isRunning
fail
test/javascript/tests/attachment_names.js
FAIL isRunning
fail
test/javascript/tests/attachment_paths.js
FAIL isRunning
fail
test/javascript/tes
> - instead of fixed test db names like `test_suite_db` that are used in
almost every test,
> we now generate a random database name for each test. The JS tests
expected db
> deletion to be synchronous, and that’s no longer the case in 2.0. Instead
of
> error-prone polling to wait for db deletion,
> On 11 Oct 2015, at 18:53, Sebastian Rothbucher
> wrote:
>
> Hi Jan,
>
> I transferred some of my findings to your branch - pls. find a PR for the
> first few tests submitted 2 your branch. I put in TODOs where either there
> is most probably a bug (filed COUCHDB-2852 and COUCHDB-2853) or we
Hi Andy,
thanks for giving this a spin!
> On 11 Oct 2015, at 22:51, Andy Wenk wrote:
>
> Hi Jan,
>
> first of all thanks a lot for the great work. I followed your instructions
> and have some notes here.
>
> * I think it should be mentioned, that one has to
>
> git checkout js-tests-on-2.0-
Hi Jan,
first of all thanks a lot for the great work. I followed your instructions
and have some notes here.
* I think it should be mentioned, that one has to
git checkout js-tests-on-2.0-wip
because when clicking the link in the email, you will be sent to the
correct branch, but when you cop
Hi Jan,
I transferred some of my findings to your branch - pls. find a PR for the
first few tests submitted 2 your branch. I put in TODOs where either there
is most probably a bug (filed COUCHDB-2852 and COUCHDB-2853) or we have to
do some more work (like making config available).
Will from the P
(I need your help deciding what to do with a bunch of tests, jump to
“Discussion” below if you don’t care about the details before.)
* * *
Hi all,
I spent some more time getting the 1.x JavaScript tests running on the cluster
port of 2.0. WIP here: https://github.com/apache/couchdb/pull/354 —
18 matches
Mail list logo
