Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
+1 I am happy to report a complete success. I followed the new Test Procedure to the letter. I have moved the notes on OpenSSL to the Troubleshooting guide: http://wiki.apache.org/couchdb/Troubleshooting If people run in to this problem, please direct them here. If it becomes a big problem, we'll call it out from the downloads page. I have added a small note to the README.Unix file mentioning this problem.
[VOTE RESULTS] was (Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3)
Hello, The final tally of the vote is: 7 +1 votes This exceeds the required minimum three +1 votes and the proposal passes. One intended vote was excluded (sorry Dirkjan, you have to say '+1'!). I shall prepare the release as soon as possible. The individual votes are as follows: Sam Bisbee: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3ccalpjnymvkpcgao7ahpjzoo1+t8xmknk0a1avetn8ok3ypyr...@mail.gmail.com%3E Klaus Trainer: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3C1319463847.4600.67.camel@devil%3E Bob Dionne: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3cd00bbdf4-462f-4f9b-8b04-a57c944cf...@dionne-associates.com%3E Randall Leeds: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCAAL6JQiu2ezN=psXNm-WOP4mRGPoOr=xpbmlz9xhk_o5puo...@mail.gmail.com%3E Filipe Manana: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCAL3q7H5dehW1DHadWCW3=zlrb+7le7subs2swqo63oyd_qe...@mail.gmail.com%3E Jan Lenhardt: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3c2e38ffe4-2d6a-4b5f-90ed-31a7be9db...@apache.org%3E Noah Slater: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447VEO1m7sas4QR6__dvmfjtpVrMLYfNOYoct2rt9=b...@mail.gmail.com%3E Thanks to everyone who voted. B. On 29 October 2011 19:16, Noah Slater nsla...@tumbolia.org wrote: +1 I am happy to report a complete success. I followed the new Test Procedure to the letter. I have moved the notes on OpenSSL to the Troubleshooting guide: http://wiki.apache.org/couchdb/Troubleshooting If people run in to this problem, please direct them here. If it becomes a big problem, we'll call it out from the downloads page. I have added a small note to the README.Unix file mentioning this problem.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Sat, Oct 29, 2011 at 8:16 PM, Noah Slater nsla...@tumbolia.org wrote: +1 I am happy to report a complete success. I followed the new Test Procedure to the letter. I have moved the notes on OpenSSL to the Troubleshooting guide: http://wiki.apache.org/couchdb/Troubleshooting Thanks for that. If people run in to this problem, please direct them here. If it becomes a big problem, we'll call it out from the downloads page. I have added a small note to the README.Unix file mentioning this problem.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
+1 All tests pass, signatures match. Mac OS X Lion, OTP R14B04, Chrome browser. On Mon, Oct 24, 2011 at 11:11 AM, Robert Newson rnew...@apache.org wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 12:41 PM, Filipe David Manana fdman...@apache.org wrote: +1 All tests pass, signatures match. Mac OS X Lion, OTP R14B04, Chrome browser. Which ssl version? Still the bug? - benoît
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 12:54 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 12:41 PM, Filipe David Manana fdman...@apache.org wrote: +1 All tests pass, signatures match. Mac OS X Lion, OTP R14B04, Chrome browser. Which ssl version? Still the bug? OpenSSL 0.9.8 built from source, exactly like it is described here: https://gist.github.com/1199903 - benoît -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 2:00 PM, Filipe David Manana fdman...@apache.org wrote: On Fri, Oct 28, 2011 at 12:54 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 12:41 PM, Filipe David Manana fdman...@apache.org wrote: +1 All tests pass, signatures match. Mac OS X Lion, OTP R14B04, Chrome browser. Which ssl version? Still the bug? OpenSSL 0.9.8 built from source, exactly like it is described here: https://gist.github.com/1199903 OK, so that's not mac osx lion as a purpose. I prefer to stay accurate here. I'm opening a bug for this issue. Not sure how to handle that, the README is the easiest solution if we don't want to stop the release. I would prefer that this notice appears in 1.1.1 release. @nslater any idea how to present that notice and where exactly ? README? a REAME.osx ? - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
Benoit, unless we abort round 3, no release note can be added until the next release. Can I get some more votes from PMC members pls? B. On 28 October 2011 13:07, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 2:00 PM, Filipe David Manana fdman...@apache.org wrote: On Fri, Oct 28, 2011 at 12:54 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 12:41 PM, Filipe David Manana fdman...@apache.org wrote: +1 All tests pass, signatures match. Mac OS X Lion, OTP R14B04, Chrome browser. Which ssl version? Still the bug? OpenSSL 0.9.8 built from source, exactly like it is described here: https://gist.github.com/1199903 OK, so that's not mac osx lion as a purpose. I prefer to stay accurate here. I'm opening a bug for this issue. Not sure how to handle that, the README is the easiest solution if we don't want to stop the release. I would prefer that this notice appears in 1.1.1 release. @nslater any idea how to present that notice and where exactly ? README? a REAME.osx ? - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 2:38 PM, Robert Newson rnew...@apache.org wrote: Benoit, unless we abort round 3, no release note can be added until the next release. That's why wanted to get opinions from others devs. But noone looks interested by this problem. If most are thinking this is a none issue, I would be quite disappointed but that's OK. I would prefer to give all the information to the user anyway and if it requires we go for a quick round 4, I would prefer to follow that way. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Oct 28, 2011, at 14:49 , Benoit Chesneau wrote: On Fri, Oct 28, 2011 at 2:38 PM, Robert Newson rnew...@apache.org wrote: Benoit, unless we abort round 3, no release note can be added until the next release. That's why wanted to get opinions from others devs. But noone looks interested by this problem. If most are thinking this is a none issue, I would be quite disappointed but that's OK. I would prefer to give all the information to the user anyway and if it requires we go for a quick round 4, I would prefer to follow that way. As far as I understand, this is an edge case and I am not worried to not have a note in that in the Readme for 1.1.1. Cheers Jan --
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Oct 24, 2011, at 12:11 , Robert Newson wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. Tested all the things and they all pass: +1 Thanks all for helping getting this release out! Cheers Jan --
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 2:51 PM, Jan Lehnardt j...@apache.org wrote: On Oct 28, 2011, at 14:49 , Benoit Chesneau wrote: On Fri, Oct 28, 2011 at 2:38 PM, Robert Newson rnew...@apache.org wrote: Benoit, unless we abort round 3, no release note can be added until the next release. That's why wanted to get opinions from others devs. But noone looks interested by this problem. If most are thinking this is a none issue, I would be quite disappointed but that's OK. I would prefer to give all the information to the user anyway and if it requires we go for a quick round 4, I would prefer to follow that way. As far as I understand, this is an edge case and I am not worried to not have a note in that in the Readme for 1.1.1. Cheers Jan -- mmm ok, thanks for the feedback. I'm +0 (and that's the first time among releases) . I will oopen a ticket about that. I'm not sure this is an edge case or not. I don't understand why it works or not, and why after 500 loop on restart etc.. - benoit - benoit.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Fri, Oct 28, 2011 at 06:17, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 2:51 PM, Jan Lehnardt j...@apache.org wrote: On Oct 28, 2011, at 14:49 , Benoit Chesneau wrote: On Fri, Oct 28, 2011 at 2:38 PM, Robert Newson rnew...@apache.org wrote: Benoit, unless we abort round 3, no release note can be added until the next release. That's why wanted to get opinions from others devs. But noone looks interested by this problem. If most are thinking this is a none issue, I would be quite disappointed but that's OK. I would prefer to give all the information to the user anyway and if it requires we go for a quick round 4, I would prefer to follow that way. As far as I understand, this is an edge case and I am not worried to not have a note in that in the Readme for 1.1.1. Cheers Jan -- mmm ok, thanks for the feedback. I'm +0 (and that's the first time among releases) . I will oopen a ticket about that. I'm not sure this is an edge case or not. I don't understand why it works or not, and why after 500 loop on restart etc.. I'm sorry I haven't been more helpful with this, Benoit, but I don't have the hardware to test it. Since I've only heard a repro case involving /_restart I'm not worried enough about a release without a note to retract my +1. However, much respect for your +0. That sounds like the right thing. I'm glad it doesn't bother you enough for a -1. I would be more comfortable if we could verify that /_restart is the only reliable way to trigger this. I'll go back and read about the changes and see if there's any way I can reason that out from the armchair. -Randall
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
Sorry for the delay, I will test and vote tomorrow. On Fri, Oct 28, 2011 at 6:55 PM, Randall Leeds randall.le...@gmail.comwrote: On Fri, Oct 28, 2011 at 06:17, Benoit Chesneau bchesn...@gmail.com wrote: On Fri, Oct 28, 2011 at 2:51 PM, Jan Lehnardt j...@apache.org wrote: On Oct 28, 2011, at 14:49 , Benoit Chesneau wrote: On Fri, Oct 28, 2011 at 2:38 PM, Robert Newson rnew...@apache.org wrote: Benoit, unless we abort round 3, no release note can be added until the next release. That's why wanted to get opinions from others devs. But noone looks interested by this problem. If most are thinking this is a none issue, I would be quite disappointed but that's OK. I would prefer to give all the information to the user anyway and if it requires we go for a quick round 4, I would prefer to follow that way. As far as I understand, this is an edge case and I am not worried to not have a note in that in the Readme for 1.1.1. Cheers Jan -- mmm ok, thanks for the feedback. I'm +0 (and that's the first time among releases) . I will oopen a ticket about that. I'm not sure this is an edge case or not. I don't understand why it works or not, and why after 500 loop on restart etc.. I'm sorry I haven't been more helpful with this, Benoit, but I don't have the hardware to test it. Since I've only heard a repro case involving /_restart I'm not worried enough about a release without a note to retract my +1. However, much respect for your +0. That sounds like the right thing. I'm glad it doesn't bother you enough for a -1. I would be more comfortable if we could verify that /_restart is the only reliable way to trigger this. I'll go back and read about the changes and see if there's any way I can reason that out from the armchair. -Randall
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Mon, Oct 24, 2011 at 12:11 PM, Robert Newson rnew...@apache.org wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. Tests pass, signatures OK on osx snow leopard, latest ubuntu and fbsd 0.8.2 . J S tests continue to fail on OSX lion from time to time with a bus error (same error that the one reported in previous bug). According filipe it is due to the openssl deprecated functions replaced by opencrypt, but it's still not clear for me why it only hangs from time to time. Anyway I don't want to block the release with a -1 so I prefer to ask. Imo we should at least add a note in the README. Also can we formally confirm the error is due to this change and why it happen from time to time? - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Mon, Oct 24, 2011 at 6:11 AM, Robert Newson rnew...@apache.org wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. Greetings, I'm +1 for the release. Everything checked out and worked *ahem* without a hiccup on Ubuntu 10.10 against xulrunner-1.9.2.23. (Pro Tip: check your /etc/ld.so.conf.d/xulrunner.conf after `apt-get upgrade`) Browser tests worked with Chromium in incognito mode ... for whatever that's worth. Cheers, -- Sam Bisbee
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
Ubuntu 10.10 (Maverick) amd64 with Erlang R14B01, Firefox 8.0, xulrunner-1.9.2.23 (./configure --with-js-lib=/usr/lib/xulrunner-devel-1.9.2.23/lib --with-js-include=/usr/lib/xulrunner-devel-1.9.2.23/include --prefix=/tmp/couchdb/install) * `diff -r` between release and git object af7a6ae52890c6c158615068f2a48d40c52ec538: ok * gpg, md5, sha1 signatures: ok * `make check`: ok * Futon tests: ok +1 Thanks all! - Klaus On Mon, 2011-10-24 at 11:11 +0100, Robert Newson wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. signature.asc Description: This is a digitally signed message part
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 3
On Mon, Oct 24, 2011 at 03:11, Robert Newson rnew...@apache.org wrote: This is the third release vote for Apache CouchDB 1.1.1 Changes since round 2; * Remove basename() dependency, fixing Windows build. Git Note: While there is no current 1.1.1 tag in our git repository, there was such a tag during round 2, which you may still have locally. It will be created again when a round is successful, and a 'git pull --tags' will correctly update your tag. It is advisable, however, to simply delete this tag locally with 'git tag -d 1.1.1'. Future releases will not create any interim tags, so this is a one-time procedure. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from: af7a6ae52890c6c158615068f2a48d40c52ec538 apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. GNU/Linux 3.0.0 Erlang R14B03 (erts-5.8.4) SMP/HiPE Firefox 8.0 Signature - OK MD5 - OK SHA1 - OK Diff - OK `make check` - OK Futon tests - OK +1 -Randall
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Thu, Oct 20, 2011 at 7:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. +0 . tests doesn't pas on 0SX lion . I think at least READMe should be updated to tell the user that OSX lion isn't a supported platform with default openssl *if* this is the reason. It's unclear for me why from time to time tests are ok. On the other hand doing a POST /_restart isn't an operatin we do often in production but I guess other operations can affected too. tests (js+ check + signature) are ok on other platforms tested (freebsd 8.2 osx 10.6) . - benoît
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 8:51 AM, Benoit Chesneau bchesn...@gmail.com wrote: +0 . tests doesn't pas on 0SX lion . I think at least READMe should be s/doesn't/don't tests (js+ check + signature) are ok on other platforms tested (freebsd 8.2 osx 10.6) . with erlang R14B03 R14B04
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
+0 OS X 10.7.2 Erlang R14B make distcheck is fine only two tests fail this time, changes and cookie_auth On Oct 20, 2011, at 1:44 PM, Robert Newson wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Thursday, 20 October 2011, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. -1 sorry from windows land. #1 libgen.h doesn't exist in our rarified air here. is this only needed to support basename in couchjs? I'm not sure what the right fix is here, as most BSDs seem to also require cdefs.h which also doesn't exist. couch@sendai /relax/couch_git/src/couchdb/priv $ make source='couch_js/util.c' object='couchjs-util.o' libtool=no \ DEPDIR=.deps depmode=none /bin/sh ../../../build-aux/depcomp \ cc.sh -DHAVE_CONFIG_H -I. -I../../.. -L/relax/tracemonkey-57a6ad20eae9/js/src/dist/lib -L/usr/local/lib -L/opt/local/lib -I/relax/otp_src_R14B03/release/win32/usr/include -I/relax/tracemonkey-57a6ad20eae9/js/src/dist/include -DXP_WIN -g -Wall -Werror -D_BSD_SOURCE -I/relax/curl/include -DCURL_STATICLIB -O2 -c -o couchjs-util.o `test -f 'couch_js/util.c' || echo './'`couch_js/util.c c:\cygwin\relax\couch_git\src\couchdb\priv\couch_js\help.h(16) : fatal error C1083: Cannot open include file: 'libgen.h': No such file or directory make: *** [couchjs-util.o] Error 2 #2 NEWS ICU update should be 4.4 not 4.2. diff --git i/NEWS w/NEWS index e62289e..d440ad0 100644 --- i/NEWS +++ w/NEWS @@ -24,7 +24,7 @@ Version 1.1.1 * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. -* Link to ICU 4.2 on Windows. +* Link to ICU 4.4 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. A+ Dave
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
Just to clarify, I reached this conclusion after seeing: http://wiki.apache.org/couchdb/Release_procedure?action=diffrev1=66rev2=67 It occurred to me that we're attempting to release without documenting what we're doing first. The documentation above is incomplete. Our official release procedure is still based in Subversion commands. I think we need to pin this down officially before proceeding. On Fri, Oct 21, 2011 at 5:53 PM, Noah Slater nsla...@tumbolia.org wrote: Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Oct 21, 2011, at 18:53 , Noah Slater wrote: Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. I think the silent consensus to not change the procedure for stable branches and ongoing votes. And I don't buy the incomplete wiki documentation missing the git and still having the SVN commands in there argument. I don't argue we should not fix it all up (we should!), but plenty of people had no trouble casting a vote that I'd say it'd be okay to run this release with wrong instructions (that we only had for two or so releases so far anyway and that we had to amend each time to clarify, so this -1 could be retroactively apply to these previous releases). That said, if this community decides we should sort out the git/tagging issue first and update the Test Procedure wiki page before releasing or even voting on 1.1.1, I'd be fine with that. Cheers Jan -- Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
That ignores the number of releases performed prior to the creation of that page. The release tarball contains the right stuff. Since the process is not fully automated and has never been fully documented, I don't think your -1 is fair. However, it seems the recent addition of help to couchjs is broken on Windows, which is release blocking, so, once it's confirmed, round 2 ends in failure too. B. On 21 October 2011 17:56, Noah Slater nsla...@tumbolia.org wrote: Just to clarify, I reached this conclusion after seeing: http://wiki.apache.org/couchdb/Release_procedure?action=diffrev1=66rev2=67 It occurred to me that we're attempting to release without documenting what we're doing first. The documentation above is incomplete. Our official release procedure is still based in Subversion commands. I think we need to pin this down officially before proceeding. On Fri, Oct 21, 2011 at 5:53 PM, Noah Slater nsla...@tumbolia.org wrote: Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 8:20 AM, Dave Cottlehuber d...@muse.net.nz wrote: On Thursday, 20 October 2011, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. -1 sorry from windows land. #1 libgen.h doesn't exist in our rarified air here. is this only needed to support basename in couchjs? I'm not sure what the right fix is here, as most BSDs seem to also require cdefs.h which also doesn't exist. Windows bites again. It only exists for basename, so we should just hardcode that to couchjs. couch@sendai /relax/couch_git/src/couchdb/priv $ make source='couch_js/util.c' object='couchjs-util.o' libtool=no \ DEPDIR=.deps depmode=none /bin/sh ../../../build-aux/depcomp \ cc.sh -DHAVE_CONFIG_H -I. -I../../.. -L/relax/tracemonkey-57a6ad20eae9/js/src/dist/lib -L/usr/local/lib -L/opt/local/lib -I/relax/otp_src_R14B03/release/win32/usr/include -I/relax/tracemonkey-57a6ad20eae9/js/src/dist/include -DXP_WIN -g -Wall -Werror -D_BSD_SOURCE -I/relax/curl/include -DCURL_STATICLIB -O2 -c -o couchjs-util.o `test -f 'couch_js/util.c' || echo './'`couch_js/util.c c:\cygwin\relax\couch_git\src\couchdb\priv\couch_js\help.h(16) : fatal error C1083: Cannot open include file: 'libgen.h': No such file or directory make: *** [couchjs-util.o] Error 2 #2 NEWS ICU update should be 4.4 not 4.2. diff --git i/NEWS w/NEWS index e62289e..d440ad0 100644 --- i/NEWS +++ w/NEWS @@ -24,7 +24,7 @@ Version 1.1.1 * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. -* Link to ICU 4.2 on Windows. +* Link to ICU 4.4 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. A+ Dave Will fix.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 10:05, Robert Newson rnew...@apache.org wrote: That ignores the number of releases performed prior to the creation of that page. The release tarball contains the right stuff. Since the process is not fully automated and has never been fully documented, I don't think your -1 is fair. Agreed. But no matter. However, it seems the recent addition of help to couchjs is broken on Windows, which is release blocking, so, once it's confirmed, round 2 ends in failure too. Confirmed. Windows doesn't have a basename() function. I apologize for jumping to the conclusion that it would. My man page for basename says that it conforms to POSIX.1-2001 and I incorrectly believed this would be portable to Windows. It appears that _splitpath_s is probably the function to use on Windows: http://msdn.microsoft.com/en-us/library/8e46eyt7.aspx Can anyone confirm that the current code works for BSD? Benoitc reported no problems with FreeBSD and successful compilation on MacOS Lion. -Randall B. On 21 October 2011 17:56, Noah Slater nsla...@tumbolia.org wrote: Just to clarify, I reached this conclusion after seeing: http://wiki.apache.org/couchdb/Release_procedure?action=diffrev1=66rev2=67 It occurred to me that we're attempting to release without documenting what we're doing first. The documentation above is incomplete. Our official release procedure is still based in Subversion commands. I think we need to pin this down officially before proceeding. On Fri, Oct 21, 2011 at 5:53 PM, Noah Slater nsla...@tumbolia.org wrote: Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
All, I'm aborting round 2 because of the lack of basename() on Windows. Round 3 to follow. nslater: Can we decide now if we're sticking with (approximately) the release procedure we've been following so far or whether we have to nail down all the git things and document before round 3 can begin? B. On 21 October 2011 18:18, Randall Leeds randall.le...@gmail.com wrote: On Fri, Oct 21, 2011 at 10:05, Robert Newson rnew...@apache.org wrote: That ignores the number of releases performed prior to the creation of that page. The release tarball contains the right stuff. Since the process is not fully automated and has never been fully documented, I don't think your -1 is fair. Agreed. But no matter. However, it seems the recent addition of help to couchjs is broken on Windows, which is release blocking, so, once it's confirmed, round 2 ends in failure too. Confirmed. Windows doesn't have a basename() function. I apologize for jumping to the conclusion that it would. My man page for basename says that it conforms to POSIX.1-2001 and I incorrectly believed this would be portable to Windows. It appears that _splitpath_s is probably the function to use on Windows: http://msdn.microsoft.com/en-us/library/8e46eyt7.aspx Can anyone confirm that the current code works for BSD? Benoitc reported no problems with FreeBSD and successful compilation on MacOS Lion. -Randall B. On 21 October 2011 17:56, Noah Slater nsla...@tumbolia.org wrote: Just to clarify, I reached this conclusion after seeing: http://wiki.apache.org/couchdb/Release_procedure?action=diffrev1=66rev2=67 It occurred to me that we're attempting to release without documenting what we're doing first. The documentation above is incomplete. Our official release procedure is still based in Subversion commands. I think we need to pin this down officially before proceeding. On Fri, Oct 21, 2011 at 5:53 PM, Noah Slater nsla...@tumbolia.org wrote: Actually, I think I'm going to give this a -1 without testing it. We still haven't ratified how releases are meant to work with Git, so I don't see that we can make a release at the present time. We need to agree on how we're going to do this, and document it in both the release procedure and test procedure before we can proceed. Unless someone else has a very good reason why this doesn't matter? On Fri, Oct 21, 2011 at 5:08 AM, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 6:04 PM, Jan Lehnardt j...@apache.org wrote: I think the silent consensus to not change the procedure for stable branches and ongoing votes. Could you clarify? And I don't buy the incomplete wiki documentation missing the git and still having the SVN commands in there argument. I don't argue we should not fix it all up (we should!), but plenty of people had no trouble casting a vote that I'd say it'd be okay to run this release with wrong instructions (that we only had for two or so releases so far anyway and that we had to amend each time to clarify, so this -1 could be retroactively apply to these previous releases). Oh, just to clarify, the Test Procedure is not blocking the release. That's a nice to have feature, and we can fix it up after the fact. Though I would not say no if someone wanted to fix it up now, in time for the third round of voting. That said, if this community decides we should sort out the git/tagging issue first and update the Test Procedure wiki page before releasing or even voting on 1.1.1, I'd be fine with that. This is the blocking issue, for me. The tagging and branching discussion happening in a parallel thread is bringing up some pretty major concerns for me, and I don't think we've nailed a consensus yet. This blocks the release from my perspective, because this is will be first release we make from Git, and whatever we do should match whatever our consensus is going forward.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 6:05 PM, Robert Newson rnew...@apache.org wrote: That ignores the number of releases performed prior to the creation of that page. The release tarball contains the right stuff. Since the process is not fully automated and has never been fully documented, I don't think your -1 is fair. Just to clarify again, I consider the official release procedure to be blocking this release. It's not only out of date, it's being actively contended in a parallel thread as we try to make this release. As this is something we will be stuck with going forward, and as something other future Apache projects will be stuck with, I think it's of paramount importance that we reach consensus before we make the release.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: nslater: Can we decide now if we're sticking with (approximately) the release procedure we've been following so far or whether we have to nail down all the git things and document before round 3 can begin? The actual text of the release procedure wiki page is unimportant. I realise we want to get this out ASAP, and I don't want to be a PITA. But we DO need to nail down how we're tagging releases. As long as we get that far, and as along as round three is tagged according to that policy, and as long as we write it down afterwards, I think I will be a happy bunny. Am I being reasonable?
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
Yes, quite reasonable. My take on tagging was to follow what we did with SVN with only minor changes to account for git. So I shall describe it. First, I create a signed tag for the release, with its intended final release value. In this case, exactly the string '1.1.1'. Then I build artifacts from the tag (which could be from a 'git archive 1.1.1' or 'git checkout 1.1.1 git clean -xdfq'). When I'm happy with the output of that phase (i.e, I've done the diff -r, make check, Futon, etc from the generated tar.gz) I upload it to people.apache.org and push the tag (so that others can verify that it matches the release artifact). In the event of a round veto, I delete the 1.1.1 tag. In the next round, I create and push a new signed 1.1.1 tag as part of the same procedure. 'git pull --tags' correctly updates anyone's existing (but now wrong) 1.1.1 tag (the man page for git-tag goes on at some length that it doesn't do that and how evil such a thing would be, but it does it anyway). The arguments in the other thread about immutable tags are laudable but irrelevant. The tags in our source control system are not the source of truth for our releases. The presence of the release on the Apache mirrors is. The entire discussion around -rcX suffixes is to avoid any confusion between the failed artifacts and the release artifact. While a genuine concern, it's not worth all this soul searching in my opinion. The real 1.1.1 comes from the mirrors. When it's available on our mirrors then it also means that the 1.1.1 tag in source control points to it (and always will). B. On 21 October 2011 18:56, Noah Slater nsla...@tumbolia.org wrote: On Fri, Oct 21, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: nslater: Can we decide now if we're sticking with (approximately) the release procedure we've been following so far or whether we have to nail down all the git things and document before round 3 can begin? The actual text of the release procedure wiki page is unimportant. I realise we want to get this out ASAP, and I don't want to be a PITA. But we DO need to nail down how we're tagging releases. As long as we get that far, and as along as round three is tagged according to that policy, and as long as we write it down afterwards, I think I will be a happy bunny. Am I being reasonable?
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
Can you post this over on the tagging thread? :) On Fri, Oct 21, 2011 at 7:13 PM, Robert Newson rnew...@apache.org wrote: Yes, quite reasonable. My take on tagging was to follow what we did with SVN with only minor changes to account for git. So I shall describe it. First, I create a signed tag for the release, with its intended final release value. In this case, exactly the string '1.1.1'. Then I build artifacts from the tag (which could be from a 'git archive 1.1.1' or 'git checkout 1.1.1 git clean -xdfq'). When I'm happy with the output of that phase (i.e, I've done the diff -r, make check, Futon, etc from the generated tar.gz) I upload it to people.apache.org and push the tag (so that others can verify that it matches the release artifact). In the event of a round veto, I delete the 1.1.1 tag. In the next round, I create and push a new signed 1.1.1 tag as part of the same procedure. 'git pull --tags' correctly updates anyone's existing (but now wrong) 1.1.1 tag (the man page for git-tag goes on at some length that it doesn't do that and how evil such a thing would be, but it does it anyway). The arguments in the other thread about immutable tags are laudable but irrelevant. The tags in our source control system are not the source of truth for our releases. The presence of the release on the Apache mirrors is. The entire discussion around -rcX suffixes is to avoid any confusion between the failed artifacts and the release artifact. While a genuine concern, it's not worth all this soul searching in my opinion. The real 1.1.1 comes from the mirrors. When it's available on our mirrors then it also means that the 1.1.1 tag in source control points to it (and always will). B. On 21 October 2011 18:56, Noah Slater nsla...@tumbolia.org wrote: On Fri, Oct 21, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: nslater: Can we decide now if we're sticking with (approximately) the release procedure we've been following so far or whether we have to nail down all the git things and document before round 3 can begin? The actual text of the release procedure wiki page is unimportant. I realise we want to get this out ASAP, and I don't want to be a PITA. But we DO need to nail down how we're tagging releases. As long as we get that far, and as along as round three is tagged according to that policy, and as long as we write it down afterwards, I think I will be a happy bunny. Am I being reasonable?
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On 21 October 2011 19:14, Paul Davis paul.joseph.da...@gmail.com wrote: On Fri, Oct 21, 2011 at 8:20 AM, Dave Cottlehuber d...@muse.net.nz wrote: On Thursday, 20 October 2011, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. -1 sorry from windows land. #1 libgen.h doesn't exist in our rarified air here. is this only needed to support basename in couchjs? I'm not sure what the right fix is here, as most BSDs seem to also require cdefs.h which also doesn't exist. Windows bites again. It only exists for basename, so we should just hardcode that to couchjs. couch@sendai /relax/couch_git/src/couchdb/priv $ make source='couch_js/util.c' object='couchjs-util.o' libtool=no \ DEPDIR=.deps depmode=none /bin/sh ../../../build-aux/depcomp \ cc.sh -DHAVE_CONFIG_H -I. -I../../.. -L/relax/tracemonkey-57a6ad20eae9/js/src/dist/lib -L/usr/local/lib -L/opt/local/lib -I/relax/otp_src_R14B03/release/win32/usr/include -I/relax/tracemonkey-57a6ad20eae9/js/src/dist/include -DXP_WIN -g -Wall -Werror -D_BSD_SOURCE -I/relax/curl/include -DCURL_STATICLIB -O2 -c -o couchjs-util.o `test -f 'couch_js/util.c' || echo './'`couch_js/util.c c:\cygwin\relax\couch_git\src\couchdb\priv\couch_js\help.h(16) : fatal error C1083: Cannot open include file: 'libgen.h': No such file or directory make: *** [couchjs-util.o] Error 2 #2 NEWS ICU update should be 4.4 not 4.2. diff --git i/NEWS w/NEWS index e62289e..d440ad0 100644 --- i/NEWS +++ w/NEWS @@ -24,7 +24,7 @@ Version 1.1.1 * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. -* Link to ICU 4.2 on Windows. +* Link to ICU 4.4 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. A+ Dave Will fix. awesome - thanks Paul. +1 for hardcoding it. Is it possisible at least to hardcode it to the target filename generated in the Makefile - softcoding perhaps? Either way, the actual file is couchjs.exe. A+ Dave
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Fri, Oct 21, 2011 at 1:26 PM, Dave Cottlehuber d...@muse.net.nz wrote: On 21 October 2011 19:14, Paul Davis paul.joseph.da...@gmail.com wrote: On Fri, Oct 21, 2011 at 8:20 AM, Dave Cottlehuber d...@muse.net.nz wrote: On Thursday, 20 October 2011, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. -1 sorry from windows land. #1 libgen.h doesn't exist in our rarified air here. is this only needed to support basename in couchjs? I'm not sure what the right fix is here, as most BSDs seem to also require cdefs.h which also doesn't exist. Windows bites again. It only exists for basename, so we should just hardcode that to couchjs. couch@sendai /relax/couch_git/src/couchdb/priv $ make source='couch_js/util.c' object='couchjs-util.o' libtool=no \ DEPDIR=.deps depmode=none /bin/sh ../../../build-aux/depcomp \ cc.sh -DHAVE_CONFIG_H -I. -I../../.. -L/relax/tracemonkey-57a6ad20eae9/js/src/dist/lib -L/usr/local/lib -L/opt/local/lib -I/relax/otp_src_R14B03/release/win32/usr/include -I/relax/tracemonkey-57a6ad20eae9/js/src/dist/include -DXP_WIN -g -Wall -Werror -D_BSD_SOURCE -I/relax/curl/include -DCURL_STATICLIB -O2 -c -o couchjs-util.o `test -f 'couch_js/util.c' || echo './'`couch_js/util.c c:\cygwin\relax\couch_git\src\couchdb\priv\couch_js\help.h(16) : fatal error C1083: Cannot open include file: 'libgen.h': No such file or directory make: *** [couchjs-util.o] Error 2 #2 NEWS ICU update should be 4.4 not 4.2. diff --git i/NEWS w/NEWS index e62289e..d440ad0 100644 --- i/NEWS +++ w/NEWS @@ -24,7 +24,7 @@ Version 1.1.1 * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. -* Link to ICU 4.2 on Windows. +* Link to ICU 4.4 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. A+ Dave Will fix. awesome - thanks Paul. +1 for hardcoding it. Is it possisible at least to hardcode it to the target filename generated in the Makefile - softcoding perhaps? Either way, the actual file is couchjs.exe. A+ Dave We can just brute force it with a Makefile conditional.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On 21 October 2011 19:56, Noah Slater nsla...@tumbolia.org wrote: On Fri, Oct 21, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: nslater: Can we decide now if we're sticking with (approximately) the release procedure we've been following so far or whether we have to nail down all the git things and document before round 3 can begin? The actual text of the release procedure wiki page is unimportant. I realise we want to get this out ASAP, and I don't want to be a PITA. But we DO need to nail down how we're tagging releases. As long as we get that far, and as along as round three is tagged according to that policy, and as long as we write it down afterwards, I think I will be a happy bunny. Am I being reasonable? Yes I agree. Further productive comments on tother thread. BTW +1 on seeing nslater in a bunny suit at the next couchcamp. Some proposals are: http://www.amazon.com/Rubies-Costume-Baby-girls-Collection-Precious/dp/B000W5OTSW http://www.amazon.com/Morris-Classic-Bunny-Small/dp/B000L5TG5O A+ Dave
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. -R
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
+1 On Wed, 2011-10-19 at 23:38 -0400, J. Lee Coltrane wrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) signature.asc Description: This is a digitally signed message part
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Wed, Oct 19, 2011 at 16:27, Robert Newson rnew...@apache.org wrote: We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. Testing in the Gentoo Linux packaging system yields the following test failures: Test Summary Report --- /var/tmp/portage/dev-db/couchdb-1.1.1/work/apache-couchdb-1.1.1/test/etap/170-os-daemons.t (Wstat: 0 Tests: 37 Failed: 0) Parse errors: Bad plan. You planned 49 tests but ran 37. /var/tmp/portage/dev-db/couchdb-1.1.1/work/apache-couchdb-1.1.1/test/etap/173-os-daemon-cfg-register.t (Wstat: 0 Tests: 27 Failed: 5) Failed tests: 4, 6, 23, 26-27 Files=44, Tests=773, 188 wallclock secs ( 0.45 usr 0.15 sys + 39.30 cusr 7.16 csys = 47.06 CPU) Result: FAIL This is with Erlang 13B04. On the other hand, the browser test suite (Firefox 9.0a2, OS X) is all clean, which is more than I can say for most releases I've tried! Thanks for the release work, let me know if I can debug those test failures somehow). Cheers, Dirkjan
Re: [VOTE] Apache CouchDB 1.1.1 Release
If anyone is currently using SpiderMonkey 1.7.0 I would be very interested if you could try a (non-builtin) filtered replication after first performing a view build (for the same database). B. On 20 October 2011 13:15, Filipe David Manana fdman...@apache.org wrote: +1 Mac OS X Lion, Google Chrome, all test pass, signatures match On Thu, Oct 20, 2011 at 11:55 AM, Klaus Trainer klaus_trai...@posteo.de wrote: Ubuntu 10.10 (Maverick) amd64 with Erlang R14B01, Firefox 8.0, xulrunner-1.9.2.23 (configure --with-js-lib=/usr/lib/xulrunner-devel-1.9.2.23/lib --with-js-include=/usr/lib/xulrunner-devel-1.9.2.23/include) * `diff -r` between release and git tag 1.1.1 (https://git-wip-us.apache.org/repos/asf/couchdb.git): ok * gpg, md5, sha1 signatures: ok * make check: ok * Futon tests: ok +1 Thanks all! - Klaus On Wed, 2011-10-19 at 15:27 +0100, Robert Newson wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release
Ubuntu 11.10 x86_64
Signatures - OK
make check - OK
make install - OK
Browsers - some FAILURES, see below
Cache and cookies is cleared, test dbs is removed before start tests (first
run). Running all.
**Firefox 7.0.1**
First run - all OK
Second run - 4 FAILURES
attachments - Assertion failed: xhr.responseText == lorem; Exception
raised: {}
auth_cache - Assertion failed: misses_after === misses_before + 1; Assertion
failed: hits_after === hits_before
list_views - Assertion 'xhr.status == 200, standard get should be 200'
failed: standard get should be 200; Assertion failed:
/head0123456789tail/.test(xhr.responseText)
rev_stemming - Assertion failed: db.open(bar, {revs:
true})._revisions.ids.length == newLimit + 1; Assertion failed: db.open(bar,
{revs: true})._revisions.ids.length == newLimit + 1
**Opera 11.51**
First run - 37 failures, see links below
http://i080.radikal.ru/1110/ab/a35a598a8922.png
http://s001.radikal.ru/i193/1110/cb/57e1ef6dd74a.png
Second run - 39 failures, added
auth_cache - Assertion failed: misses_after === (misses_before + 1)
Assertion failed: hits_after === hits_before
replication - Exception raised: {message:JSON.parse: Unable to parse
value: }
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 3:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit just after typed that I realised that refuge is also based on current trunk... - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 3:29 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit just after typed that I realised that refuge is also based on current trunk... - benoit which means there's maybe a problem on 1.1.1 . Did anyone tried withe same conf? - benoît
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 3:47 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men. Like I said i've no problem on refuge though. Yes all apps starts crypt but here: 2 crypto:start(). ok 3 init:restart(). ok 4 Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.8.5 (abort with ^G) 1 works. So it maybe not related to crypto or openssl. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 2:57 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:47 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men. Like I said i've no problem on refuge though. Yes all apps starts crypt but here: 2 crypto:start(). ok 3 init:restart(). ok 4 Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.8.5 (abort with ^G) 1 works. So it maybe not related to crypto or openssl. The openssl issue didn't happen always, only sometimes. Try running the following bash loop against trunk/refuge: $ for i in `seq 1 1000`; do curl -s -H 'Content-Type: application/json' -X POST http://localhost:5984/_restart ; sleep 1; done Se then if you get a bus error, seg fault or the vm simply doesn't restart and no error gets sent to the console. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 6:05 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:57 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:47 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men. Like I said i've no problem on refuge though. Yes all apps starts crypt but here: 2 crypto:start(). ok 3 init:restart(). ok 4 Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.8.5 (abort with ^G) 1 works. So it maybe not related to crypto or openssl. The openssl issue didn't happen always, only sometimes. Try running the following bash loop against trunk/refuge: $ for i in `seq 1 1000`; do curl -s -H 'Content-Type: application/json' -X POST http://localhost:5984/_restart ; sleep 1; done Se then if you get a bus error, seg fault or the vm simply doesn't restart and no error gets sent to the console. - benoit I will trust you on that one, I can't test right now, I'm at ogdcamp and no more battery on my lappy. Old erlang was given me an error each time, not sure what changed since. If this is the case I think we should provide a warning during compilation anyway. Like for couchjs spidermonkey, I think it's our responsibility to warn the user that something can happen on this platform,
Re: [VOTE] Apache CouchDB 1.1.1 Release
Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. On 20 October 2011 14:57, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:47 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit -- Filipe David Manana, Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men. Like I said i've no problem on refuge though. Yes all apps starts crypt but here: 2 crypto:start(). ok 3 init:restart(). ok 4 Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.8.5 (abort with ^G) 1 works. So it maybe not related to crypto or openssl. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Wed, Oct 19, 2011 at 10:38 PM, J. Lee Coltrane l...@projectmastermind.com wrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. CouchDB is intended to be a server that can be accessed from HTTP clients. Browsers are but one of a huge range of clients. I do agree that there should be a browser based test suite, but I'm proposing that these browser based tests should be testing the browser and not testing CouchDB internals. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) And I can provide examples where having a stateful caching client merely exists to confound the test code. The issue is that using a stateful caching client means that all tests have to account for this, even tests that have nothing to do with such things. These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. There are some tests that make use of XHR directly which are incapable of being run from the CLI test runner for one. There are also issues in differences of caching implementations. There are even differences of caching against localhost vs a remote server. I consider every time I've had to diagnose a difference in browser behavior as an example of precisely why (most of) these tests do not belong in a browser. Not only is this a waste of time, it merely serves to make the test suite less trustable when an error occurs. We can hand wave about cleaning up the tests to make them more reliable, but that's ignoring the fact that we're running the test suite in huge monolithic environments that have a decades long history of maddeningly subtle different semantics. I do see significant benefits to using the same javascript test code in all environments we test. What's the benefit to maintaing assertions in the browser about view output according to the UCA. Or whether or not the database is leaking file descriptors. Or couch_os_process is properly caching couchjs processes? -Lee (irc: coltr) I don't mean to be cranky at you directly, but I am quite tired of dealing with browsers to test a database. It was a bad idea to start with and I've been trying to argue for the change for years now.
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers.
Re: [VOTE] Apache CouchDB 1.1.1 Release
FWIW, the patch attached to COUCHDB-1310 (https://issues.apache.org/jira/browse/COUCHDB-1310) will fix a great many (all, afaik) of the futon test hangs (the cases where the tests get stuck, and never complete). Without this patch, I was never able to get a complete run through the browser tests in 1.1.1 RC1. With the patch, I still get test failures, but at least I can get through all the tests without restarting the browser. The patch is tiny -- it just swaps the order of two lines of code, in the '/_restart' handler, so that the http response gets written *before* the server is restarted (rather than after). As test instability continues to be a hot topic, maybe this patch is worth considering for inclusion in the next 1.1.1 RC? -Lee On Oct 20, 2011, at 12:25 PM, Benoit Chesneau wrote: On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release
Too late. I'm inclined to work with Paul Davis and make 1.1.1 the last time that there *is* a Futon test suite. B. On 20 October 2011 18:54, J. Lee Coltrane l...@projectmastermind.com wrote: FWIW, the patch attached to COUCHDB-1310 (https://issues.apache.org/jira/browse/COUCHDB-1310) will fix a great many (all, afaik) of the futon test hangs (the cases where the tests get stuck, and never complete). Without this patch, I was never able to get a complete run through the browser tests in 1.1.1 RC1. With the patch, I still get test failures, but at least I can get through all the tests without restarting the browser. The patch is tiny -- it just swaps the order of two lines of code, in the '/_restart' handler, so that the http response gets written *before* the server is restarted (rather than after). As test instability continues to be a hot topic, maybe this patch is worth considering for inclusion in the next 1.1.1 RC? -Lee On Oct 20, 2011, at 12:25 PM, Benoit Chesneau wrote: On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Thu, Oct 20, 2011 at 19:44, Robert Newson rnew...@apache.org wrote: We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. Ran it through the Gentoo packaging system again. Mixed bag: make check is now clean, but the browser test suite has three reproducible failures: http://couchdb.couchdb.org/_utils/document.html?test_suite_reports/39e9ee253b2c269761c75c9049809d86 Linux, Erlang 13B04, SpiderMonkey from xulrunner-1.9.2.15, Firefox 9.0a2. Cheers, Dirkjan
Re: [VOTE] Apache CouchDB 1.1.1 Release
Interesting, this patch seems like a worthwhile thing to do regardless of the tests, if I understand it correctly. If restart cause the response to not be sent, then sending a 202 first will help at least the caller to know the restart was initiated. On Oct 20, 2011, at 1:54 PM, J. Lee Coltrane wrote: FWIW, the patch attached to COUCHDB-1310 (https://issues.apache.org/jira/browse/COUCHDB-1310) will fix a great many (all, afaik) of the futon test hangs (the cases where the tests get stuck, and never complete). Without this patch, I was never able to get a complete run through the browser tests in 1.1.1 RC1. With the patch, I still get test failures, but at least I can get through all the tests without restarting the browser. The patch is tiny -- it just swaps the order of two lines of code, in the '/_restart' handler, so that the http response gets written *before* the server is restarted (rather than after). As test instability continues to be a hot topic, maybe this patch is worth considering for inclusion in the next 1.1.1 RC? -Lee On Oct 20, 2011, at 12:25 PM, Benoit Chesneau wrote: On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
The list_views and attachments error are symptoms of not clearing your browser cache before starting. I'm not sure about the rev_stemming one. Please include all information within the text of your post. These are all archived and form a historical record of the release process. B. On 20 October 2011 19:31, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Thu, Oct 20, 2011 at 19:44, Robert Newson rnew...@apache.org wrote: We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. Ran it through the Gentoo packaging system again. Mixed bag: make check is now clean, but the browser test suite has three reproducible failures: http://couchdb.couchdb.org/_utils/document.html?test_suite_reports/39e9ee253b2c269761c75c9049809d86 Linux, Erlang 13B04, SpiderMonkey from xulrunner-1.9.2.15, Firefox 9.0a2. Cheers, Dirkjan
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile. -Randall
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Thu, Oct 20, 2011 at 13:44, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B. Hey, so that was smooth. Everything passes, first time around, with no problems. +1
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile. -Randall We've had these tests for three years or more now. Perhaps I'm just being dense today but I can't think of a single specific case where testing things in the browser has lead to a bug report/fix that we wouldn't have found with pure CLI tests. The only thing that I'm aware that the tests have done for us is required us to exert a nontrivial amount of effort to keep them running in multiple browser environments. I have no interest in maintaing these as tests runnable in the browser. I want to create a CLI test environment that promotes stable, repeatable, concise tests. Running these in a browser is the antithesis to such an environment.
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
I'll also note that the bug that killed round 1 of 1.1.1 was not found by any test we currently have. All it would have taken is a test that did any map call followed by almost any other bit of javascript (and sm 1.7.0). On 20 October 2011 21:22, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.comwrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile. -Randall We've had these tests for three years or more now. Perhaps I'm just being dense today but I can't think of a single specific case where testing things in the browser has lead to a bug report/fix that we wouldn't have found with pure CLI tests. The only thing that I'm aware that the tests have done for us is required us to exert a nontrivial amount of effort to keep them running in multiple browser environments. I have no interest in maintaing these as tests runnable in the browser. I want to create a CLI test environment that promotes stable, repeatable, concise tests. Running these in a browser is the antithesis to such an environment.
Re: [VOTE] Apache CouchDB 1.1.1 Release
-1 On Thu, 2011-10-20 at 18:57 +0100, Robert Newson wrote: Too late. I'm inclined to work with Paul Davis and make 1.1.1 the last time that there *is* a Futon test suite. B. On 20 October 2011 18:54, J. Lee Coltrane l...@projectmastermind.com wrote: FWIW, the patch attached to COUCHDB-1310 (https://issues.apache.org/jira/browse/COUCHDB-1310) will fix a great many (all, afaik) of the futon test hangs (the cases where the tests get stuck, and never complete). Without this patch, I was never able to get a complete run through the browser tests in 1.1.1 RC1. With the patch, I still get test failures, but at least I can get through all the tests without restarting the browser. The patch is tiny -- it just swaps the order of two lines of code, in the '/_restart' handler, so that the http response gets written *before* the server is restarted (rather than after). As test instability continues to be a hot topic, maybe this patch is worth considering for inclusion in the next 1.1.1 RC? -Lee On Oct 20, 2011, at 12:25 PM, Benoit Chesneau wrote: On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit signature.asc Description: This is a digitally signed message part
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
+1 Everything worked great. Wasn't able to check the pgp key because my gpg client is acting up at the moment. Cheers, -- Sam Bisbee On Thu, Oct 20, 2011 at 1:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release
Hehe, given the fact that the voting round has been aborted, I thought it would be clear that it relates to your most recent reply ;) Sorry, I've missed that the respective thread for that topic (i.e., futon tests) had grown meanwhile. I should have better replied on that one. - K On Thu, 2011-10-20 at 21:38 +0100, Robert Newson wrote: What is that -1 related to? On 20 October 2011 21:36, Klaus Trainer klaus_trai...@posteo.de wrote: -1 On Thu, 2011-10-20 at 18:57 +0100, Robert Newson wrote: Too late. I'm inclined to work with Paul Davis and make 1.1.1 the last time that there *is* a Futon test suite. B. On 20 October 2011 18:54, J. Lee Coltrane l...@projectmastermind.com wrote: FWIW, the patch attached to COUCHDB-1310 (https://issues.apache.org/jira/browse/COUCHDB-1310) will fix a great many (all, afaik) of the futon test hangs (the cases where the tests get stuck, and never complete). Without this patch, I was never able to get a complete run through the browser tests in 1.1.1 RC1. With the patch, I still get test failures, but at least I can get through all the tests without restarting the browser. The patch is tiny -- it just swaps the order of two lines of code, in the '/_restart' handler, so that the http response gets written *before* the server is restarted (rather than after). As test instability continues to be a hot topic, maybe this patch is worth considering for inclusion in the next 1.1.1 RC? -Lee On Oct 20, 2011, at 12:25 PM, Benoit Chesneau wrote: On Thu, Oct 20, 2011 at 6:23 PM, Robert Newson rnew...@apache.org wrote: Hi All, Thanks for all the responses so far. Unfortunately I am aborting this round. It turns out there is a serious bug in this 1.1.1 candidate when using SpiderMonkey 1.7.0. Instead of sealing the 'doc' parameter to views, we seal the object that defines the seal function, which then causes all kinds of 'X is read-only' events. It's a one word fix, so a new 1.1.1 candidate will be out very soon, and it should not invalidate any of these results. B. :( It would worth to look at this erlang warning too imo. Hopefully i will have some wifi at the hotel tonight.I will see if I can make it. - benoit signature.asc Description: This is a digitally signed message part
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 2:28 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, Oct 20, 2011 at 3:17 PM, Filipe David Manana fdman...@apache.org wrote: On Thu, Oct 20, 2011 at 2:12 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. make check pass, but when running js tests I got the following error (reproducible from time to time) : [info] [0.1915.0] Stopping all ongoing replications because the replicator database was deleted or changed Apache CouchDB 1.1.1 (LogLevel=info) is starting. Segmentation fault: 11 configuration : rb1404, osx lion (last update) That's likely the OpenSSL issue on Lion. If init:restart/0 is invoked and the crypto application was loaded (CouchDB's case) the VM crashes with either a bus error, segmentation fault or no error message at all. Have you tried building OTP like in https://gist.github.com/1199903 ? I had exactly the same issue. - benoit Shouldn't it be fixed in r144b04? \ Nop, not fixed in r14b04 unfortunately. And it's independent of the couch codebase, since all start the crypto application. ALso I don't reproduce it at all on refuge when running tests, s it may be due to the way we compile couch. - benoit
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
+1 on all the stuff Paul said. On Thu, Oct 20, 2011 at 9:25 PM, Robert Newson rnew...@apache.org wrote: I'll also note that the bug that killed round 1 of 1.1.1 was not found by any test we currently have. All it would have taken is a test that did any map call followed by almost any other bit of javascript (and sm 1.7.0). On 20 October 2011 21:22, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile. -Randall We've had these tests for three years or more now. Perhaps I'm just being dense today but I can't think of a single specific case where testing things in the browser has lead to a bug report/fix that we wouldn't have found with pure CLI tests. The only thing that I'm aware that the tests have done for us is required us to exert a nontrivial amount of effort to keep them running in multiple browser environments. I have no interest in maintaing these as tests runnable in the browser. I want to create a CLI test environment that promotes stable, repeatable, concise tests.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Thu, Oct 20, 2011 at 6:57 PM, Robert Newson rnew...@apache.org wrote: Too late. I'm inclined to work with Paul Davis and make 1.1.1 the last time that there *is* a Futon test suite. :D
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: [VOTE] Apache CouchDB 1.1.1 Release, Round 2
On Thu, Oct 20, 2011 at 7:16 PM, Noah Slater nsla...@tumbolia.org wrote: Can someone provide assistance on the new Test procedure please: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201110.mbox/%3CCA+Y+447FXqVGx8ow=ewqm86cn9epb1cnbmvhk9ku4ogujby...@mail.gmail.com%3E I am not sure how best to update the workflow for Git. git clone http://git-wip-us.apache.org/repos/asf/couchdb.git git checkout X.Y.Z The more I think about it, the more I think the requirement to not require a local checkout is silly. You're still requiring a copy of the VCS locally. Just because Git can make it a super awesome local copy of the entire repo seems like something we shouldn't penalize it for. Granted, Noah usually has a reasoning, so maybe I'm missing something else? This is important. *waves hands* On Thu, Oct 20, 2011 at 6:44 PM, Robert Newson rnew...@apache.org wrote: This is the second release vote for Apache CouchDB 1.1.1 Changes since round 1; * Fix object sealing with SpiderMonkey 1.7.0 * Update CHANGES/NEWS to reflect COUCHDB-1129 * Fix JavaScript CLI test runner We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Test ALL the things. B.
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
http://www.youtube.com/watch?feature=player_detailpagev=G6j5bve7O5E#t=109s On Thu, Oct 20, 2011 at 7:08 PM, Noah Slater nsla...@tumbolia.org wrote: +1 on all the stuff Paul said. On Thu, Oct 20, 2011 at 9:25 PM, Robert Newson rnew...@apache.org wrote: I'll also note that the bug that killed round 1 of 1.1.1 was not found by any test we currently have. All it would have taken is a test that did any map call followed by almost any other bit of javascript (and sm 1.7.0). On 20 October 2011 21:22, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile. -Randall We've had these tests for three years or more now. Perhaps I'm just being dense today but I can't think of a single specific case where testing things in the browser has lead to a bug report/fix that we wouldn't have found with pure CLI tests. The only thing that I'm aware that the tests have done for us is required us to exert a nontrivial amount of effort to keep them running in multiple browser environments. I have no interest
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
Wait, did you post that because me and you rock this project like the Beatles rocked America? Or did you post it with the intention of the song She Loves You being a sort of meta-commentary on our enviable, and now infamous, bromance? On Fri, Oct 21, 2011 at 5:13 AM, Paul Davis paul.joseph.da...@gmail.comwrote: http://www.youtube.com/watch?feature=player_detailpagev=G6j5bve7O5E#t=109s On Thu, Oct 20, 2011 at 7:08 PM, Noah Slater nsla...@tumbolia.org wrote: +1 on all the stuff Paul said. On Thu, Oct 20, 2011 at 9:25 PM, Robert Newson rnew...@apache.org wrote: I'll also note that the bug that killed round 1 of 1.1.1 was not found by any test we currently have. All it would have taken is a test that did any map call followed by almost any other bit of javascript (and sm 1.7.0). On 20 October 2011 21:22, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it shouldn't) or that we should feel 100% obligated to make sure they pass in 100% of environments (we can't and shouldn't), but J. Lee's point about how keeping such tests around can sometimes expose interesting problems we wouldn't otherwise see, possible outside the CouchDB codebase even, is worthwhile.
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
Honestly, I was looking for the video of the one lady screaming to provide commentary on they I agree with what he said comment. But I failed slightly, but only slightly enough to illicit an awesome introspection on a random Beatles video. On Thu, Oct 20, 2011 at 11:17 PM, Noah Slater nsla...@tumbolia.org wrote: Wait, did you post that because me and you rock this project like the Beatles rocked America? Or did you post it with the intention of the song She Loves You being a sort of meta-commentary on our enviable, and now infamous, bromance? On Fri, Oct 21, 2011 at 5:13 AM, Paul Davis paul.joseph.da...@gmail.comwrote: http://www.youtube.com/watch?feature=player_detailpagev=G6j5bve7O5E#t=109s On Thu, Oct 20, 2011 at 7:08 PM, Noah Slater nsla...@tumbolia.org wrote: +1 on all the stuff Paul said. On Thu, Oct 20, 2011 at 9:25 PM, Robert Newson rnew...@apache.org wrote: I'll also note that the bug that killed round 1 of 1.1.1 was not found by any test we currently have. All it would have taken is a test that did any map call followed by almost any other bit of javascript (and sm 1.7.0). On 20 October 2011 21:22, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:45 PM, Randall Leeds randall.le...@gmail.com wrote: On Thu, Oct 20, 2011 at 13:42, Paul Davis paul.joseph.da...@gmail.com wrote: On Thu, Oct 20, 2011 at 1:38 AM, Randall Leeds rand...@apache.org wrote: On Wed, Oct 19, 2011 at 23:38, J. Lee Coltrane l...@projectmastermind.comwrote: For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr) +1 Verify Installation could grow into a suite of browser/futon tests that verify that futon (and apps in general) work, including interactions with proxies and the like. Sure. Client tests that test the client are fine. The test suite for developers should run cleanly from the CLI as part of make check, but continue to be exposed in futon. We should work to be sure they function as well as possible, for the reasons you provide. Blargh no. Server tests should be testing the server. The entire point of moving to the command line is so that we don't have to maintain the Futon test suite. Just look at the 1.1.1 thread (or damn near any release thread) and the wildly varying reports of test output. The situation is just a waste of time for everyone involved. I think the JS testing situation is a great place for people to jump in and help out, especially with the browser environment diversity. Sure, but I don't see what this has to do with browsers. People who aren't into the internals can help to fix the suite to work in different browser environments. That's all I meant. Seeing as I'm having a Negative Nancy day, I'll just ask rhetorically, If these people exist, why do I not see anything in JIRA? I suggested that the CLI tests be exposed in Futon because I think there are probably some JS heads in this community who wouldn't have too much trouble fixing a lot of the user agent related issues in the test suite. I didn't mean to suggest that it should continue to be part of the release procedure (it
Re: [VOTE] Apache CouchDB 1.1.1 Release
Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
The auth cache test is a bit temperamental. Does it *always* fails for you? Did you clear your browser cache? Both of those test pass for me on Chrome 14 and FF 4. B. On 19 October 2011 16:45, Sam Bisbee s...@sbisbee.com wrote: Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
Did I say 4? I meant 7. On 19 October 2011 17:14, Robert Newson rnew...@apache.org wrote: The auth cache test is a bit temperamental. Does it *always* fails for you? Did you clear your browser cache? Both of those test pass for me on Chrome 14 and FF 4. B. On 19 October 2011 16:45, Sam Bisbee s...@sbisbee.com wrote: Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
http://www.youtube.com/watch?v=50jVa25gmWs On Wed, Oct 19, 2011 at 11:24 AM, Robert Newson rnew...@apache.org wrote: Did I say 4? I meant 7. On 19 October 2011 17:14, Robert Newson rnew...@apache.org wrote: The auth cache test is a bit temperamental. Does it *always* fails for you? Did you clear your browser cache? Both of those test pass for me on Chrome 14 and FF 4. B. On 19 October 2011 16:45, Sam Bisbee s...@sbisbee.com wrote: Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
Hi Stefan, Sadly, I don't expect the test to pass every single time (for various reasons). If each of the tests passes, that's what I need to hear. We will improve the stability of the test suite over time. B. On 19 October 2011 19:21, Stefan Kögl koeglste...@gmail.com wrote: Hi, On Wed, Oct 19, 2011 at 4:27 PM, Robert Newson rnew...@apache.org wrote: Since you have read this far, you MUST vote. I've followed the test procedure. Everything is fine until the browser tests: The changes test sometimes fails with the following error Exception raised: timeout: undefined The stats test always fails with Assertion 'triggered, We managed to force a all_dbs_active error.' failed: We managed to force a all_dbs_active error. Can I provide any further details for debugging? -- Stefan
Re: [VOTE] Apache CouchDB 1.1.1 Release
Yeah, it looks like it's just an unstable test. Which makes me wonder why we even have it or include it in the release process. Same with jsonp. So I guess I'm going to a +1 now, though I'm not happy about it. :) -- Sam Bisbee On Wed, Oct 19, 2011 at 12:14 PM, Robert Newson rnew...@apache.org wrote: The auth cache test is a bit temperamental. Does it *always* fails for you? Did you clear your browser cache? Both of those test pass for me on Chrome 14 and FF 4. B. On 19 October 2011 16:45, Sam Bisbee s...@sbisbee.com wrote: Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
OS X 10.7.2, Erlang R14B03 * signatures: OK * make check: OK * browser tests: OK (using Chrome 16.0.912.0) +1, good work! On 19.10.2011, at 16:27, Robert Newson wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Oct 19, 2011, at 21:25 , Sam Bisbee wrote: Yeah, it looks like it's just an unstable test. Which makes me wonder why we even have it or include it in the release process. It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'd still consider having the test better than not having it at all :) Cheers Jan -- Same with jsonp. So I guess I'm going to a +1 now, though I'm not happy about it. :) -- Sam Bisbee On Wed, Oct 19, 2011 at 12:14 PM, Robert Newson rnew...@apache.org wrote: The auth cache test is a bit temperamental. Does it *always* fails for you? Did you clear your browser cache? Both of those test pass for me on Chrome 14 and FF 4. B. On 19 October 2011 16:45, Sam Bisbee s...@sbisbee.com wrote: Thanks for managing this one Rob! Signatures, unit tests, etc. are all fine on Ubuntu maverick. However, I'm seeing Futon test failures in both FF 3.6.18 and Chromium 12.0.742.112: - auth_cache fails with: 1. Assertion failed: misses_after === misses_before + 1 2. Assertion failed: hits_after === hits_before - jsonp only fails in FF with: 1. Assertion failed: expected 'text/javascript', got 'application/json' So at the moment I am -1. Cheers, -- Sam Bisbee On Wed, Oct 19, 2011 at 10:27 AM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
+0 make distcheck runs fine, all etaps pass Futon tests fail in FF -- server admin gets out of whack at replicator and all tests thereafter to the end fail Chrome -- same problem, this time the fails start at cookie_auth -- but it appears to be the same issue all the usual remedies, clearing the cache, wiping the filesystem and starting over, all fail. I'm sure it's the usual browser problems, I do notice though that it's been a while since I've seen them all pass On Oct 19, 2011, at 10:27 AM, Robert Newson wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Wed, Oct 19, 2011 at 10:27, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote. Tested on Ubuntu 11.10, GNU/Linux 3.0.0, Erlang R14B03, Firefox 8.0, SpiderMonkey 1.8.5 Signature OK MD5 OK SHA1 OK `make check` OK Futon tests OK +1 Thanks! Great point release! -Randall
futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Wed, Oct 19, 2011 at 3:52 PM, Jan Lehnardt j...@apache.org wrote: On Oct 19, 2011, at 21:25 , Sam Bisbee wrote: Yeah, it looks like it's just an unstable test. Which makes me wonder why we even have it or include it in the release process. It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'm all for improvement. :) But is this improvement being tracked anywhere, JIRA or otherwise? And if not, then could it be? I'm sure that folks (self included) would be willing to pitch in if we knew what had to be done. I'd still consider having the test better than not having it at all :) I semi remember this being discussed before, but are the Futon tests meant to test CouchDB, Futon, or the integration of the two? Cheers, -- Sam Bisbee
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Wed, Oct 19, 2011 at 5:00 PM, Sam Bisbee s...@sbisbee.com wrote: On Wed, Oct 19, 2011 at 3:52 PM, Jan Lehnardt j...@apache.org wrote: On Oct 19, 2011, at 21:25 , Sam Bisbee wrote: Yeah, it looks like it's just an unstable test. Which makes me wonder why we even have it or include it in the release process. It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'm all for improvement. :) But is this improvement being tracked anywhere, JIRA or otherwise? And if not, then could it be? I'm sure that folks (self included) would be willing to pitch in if we knew what had to be done. There was a thread about splitting Futon tests out and making them proper CLI tests that are run as part of `make check` and become actual release blockers. I have often and loudly voiced my support of this approach. I refer you to the number of varying reports for 1.1.1 with various browsers as Exhibit A in favor of this switch. I'd still consider having the test better than not having it at all :) I semi remember this being discussed before, but are the Futon tests meant to test CouchDB, Futon, or the integration of the two? The test suite is there to test CouchDB. There's some merit to testing Futon/Browser access as well. Jan's recent approach to the verify installation seems to me like a good way forward. We could use a small number of tests that check various browser capabilities and what not. But I think a large amount of the Futon test code should be permanently removed from the browser based test runner. Cheers, -- Sam Bisbee
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
On Wed, Oct 19, 2011 at 6:12 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Wed, Oct 19, 2011 at 5:00 PM, Sam Bisbee s...@sbisbee.com wrote: On Wed, Oct 19, 2011 at 3:52 PM, Jan Lehnardt j...@apache.org wrote: On Oct 19, 2011, at 21:25 , Sam Bisbee wrote: Yeah, it looks like it's just an unstable test. Which makes me wonder why we even have it or include it in the release process. It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'm all for improvement. :) But is this improvement being tracked anywhere, JIRA or otherwise? And if not, then could it be? I'm sure that folks (self included) would be willing to pitch in if we knew what had to be done. There was a thread about splitting Futon tests out and making them proper CLI tests that are run as part of `make check` and become actual release blockers. I have often and loudly voiced my support of this approach. I refer you to the number of varying reports for 1.1.1 with various browsers as Exhibit A in favor of this switch. Yeah, that sounds like the thread I was remembering. For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. I'd still consider having the test better than not having it at all :) I semi remember this being discussed before, but are the Futon tests meant to test CouchDB, Futon, or the integration of the two? The test suite is there to test CouchDB. There's some merit to testing Futon/Browser access as well. Jan's recent approach to the verify installation seems to me like a good way forward. We could use a small number of tests that check various browser capabilities and what not. But I think a large amount of the Futon test code should be permanently removed from the browser based test runner. I think that there is merit in unit testing futon.js and jquery.couch.js, which just makes those things sound more like their own project. As a side, semi related note I have always wondered why jquery.couch.js was part of Apache CouchDB. For browser/Futon checks, it seems to me that these are more of environmental checks: is the right version of jquery being used, is it a supported browser, etc. Verifying the installation is running `make check`, turning on the server (which should be checking more permissions), and then running your software. Cheers, -- Sam Bisbee
Re: [VOTE] Apache CouchDB 1.1.1 Release
Following the test procedure, I get as far as this command: svn export http://svn.apache.org/repos/asf/couchdb/tags/1.1.0/tmp/couchdb/tag/1.1.0 Obviously, we can't instruct people to do this any more, because we use Git. What should we replace this step with? We need a quick and painless way to check out the tag into a temporary directory. Ideally, whatever we recomend shouldn't rely on the user already having a clone of the main repository. Current suggestions from Paul: git archive v1.2.9 | tar -C /tmp/new/path -xv Problem: It requires you to do this from an existing clone, which will be a pain to set up if you don't have one. And if you do have one, you will need to make sure it is up to date. Lots of potential for problems, errors, or hassle. wget http://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=snapshot;h=e37148e14bdaf88a0a568edbade6cf9101afb4af;sf=tgz Problem: Requires you to substitute the commit hash of the tag, which will be awkward and error prone. Any other ideas? On Wed, Oct 19, 2011 at 3:27 PM, Robert Newson rnew...@apache.org wrote: This is the release vote for Apache CouchDB 1.1.1 Changes in this release: * Support SpiderMonkey 1.8.5 * Add configurable maximum to the number of bytes returned by _log. * Allow CommonJS modules to be an empty string. * Bump minimum Erlang version to R13B02. * Do not run deleted validate_doc_update functions. * ETags for views include current sequence if include_docs=true. * Fix bug where duplicates can appear in _changes feed. * Fix bug where update handlers break after conflict resolution. * Fix bug with _replicator where include filter could crash couch. * Fix crashes when compacting large views. * Fix file descriptor leak in _log * Fix missing revisions in _changes?style=all_docs. * Improve handling of compaction at max_dbs_open limit. * JSONP responses now send text/javascript for Content-Type. * Link to ICU 4.2 on Windows. * Permit forward slashes in path to update functions. * Reap couchjs processes that hit reduce_overflow error. * Status code can be specified in update handlers. * Support provides() in show functions. * _view_cleanup when ddoc has no views now removes all index files. * max_replication_retry_count now supports infinity. * Fix replication crash when source database has a document with empty ID. * Fix deadlock when assigning couchjs processes to serve requests. * Fixes to the document multipart PUT API. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~rnewson/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.1.1 tag in Git: apache-couchdb-1.1.1.tar.gz apache-couchdb-1.1.1.tar.gz.md5 apache-couchdb-1.1.1.tar.gz.asc apache-couchdb-1.1.1.tar.gz.sha Since you have read this far, you MUST vote.
Re: [VOTE] Apache CouchDB 1.1.1 Release
On Wed, Oct 19, 2011 at 8:52 PM, Jan Lehnardt j...@apache.org wrote: It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'd still consider having the test better than not having it at all :) I disagree, of course. :) Unstable tests are a massive problem, because they reduce the overall trust we have in the test suite. For a test suite to be meaningful, it needs to be a rock solid contract between the developers and the testers, or users. I think I'm preaching to the choir here though. As far as I understand it, the current goal is to move the test suite to a CLI version, and morph the Futon tests into a high-level sanity check.
Re: [VOTE] Apache CouchDB 1.1.1 Release
You will excuse this duplication of topic forking. :) It was sent before the issue was taken to a new thread, but held up in moderation. On Wed, Oct 19, 2011 at 10:56 PM, Noah Slater nsla...@tumbolia.org wrote: On Wed, Oct 19, 2011 at 8:52 PM, Jan Lehnardt j...@apache.org wrote: It is only unstable in certain environments and we are constantly improving all tests to be more stable in all environments, but the browser world is harsh :) I'd still consider having the test better than not having it at all :) I disagree, of course. :) Unstable tests are a massive problem, because they reduce the overall trust we have in the test suite. For a test suite to be meaningful, it needs to be a rock solid contract between the developers and the testers, or users. I think I'm preaching to the choir here though. As far as I understand it, the current goal is to move the test suite to a CLI version, and morph the Futon tests into a high-level sanity check.
Re: futon tests (Was: Re: [VOTE] Apache CouchDB 1.1.1 Release)
For what it's worth, a CLI based test system is what I was imagining as well. Take Futon out of the mix and test CouchDB. IMO, If CouchDB is intended to be a server that can be accessed from the browser directly, then there should continue to be some kind of browser-based test suite that would serve to confirm this capability. I have been looking closely at the Futon tests in 1.1.0 for the last several days, with the idea that I might begin to clean them up a bit as time permits. I have found that, while some of these test failures are totally bogus, *some* of them actually do stem from real issues -- minor incompatibilities between CouchDB's http interface, and the internal mechanisms of modern browsers (XHR, caching, etc). These are problems that we're not going to catch with a stateless, cache-less http client running on the CLI. (I can provide examples) These issues have the potential to cause real problems for developers of real browser-based apps in the wild. That means, there's valuable info to be gathered from the browser tests, Iff we can clean them up, and make them behave consistently; so that when they fail or succeed, we can actually trust the results. After digging around a good bit, I can see no reason why the existing tests couldn't be cleaned up and made to work correctly in all current versions of major browsers. I also see no reason why the same tests couldn't be used successfully from the CLI and `make check` as well. I do see significant benefits to using the same javascript test code in all environments we test. -Lee (irc: coltr)
