* Mac OS X 10.15.3 (Catalina) * Erlang/OTP 22 [erts-10.6.2] * All sigs are ok * configure ok * make check:
ERROR: One or more eunit tests failed. ERROR: eunit failed while processing /private/tmp/couchdb/dist/apache-couchdb-3.0.0/src/chttpd: rebar_abort make[1]: *** [eunit] Error 1 make: *** [check] Error 2 Not sure what the difference is between eunit and check. What I found is this: module 'chttpd_view_test' chttpd view tests chttpd_view_test:75: should_succeed_on_view_with_queries_keys...*failed* in function chttpd_view_test:'-should_succeed_on_view_with_queries_keys/1-fun-2-'/1 (test/eunit/chttpd_view_test.erl, line 77) in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71) in call from eunit_proc:run_test/1 (eunit_proc.erl, line 510) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 335) in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 493) in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 435) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 325) in call from eunit_proc:run_group/2 (eunit_proc.erl, line 549) **error:{badmatch,{error,req_timedout}} output:<<"">> chttpd_view_test:91: should_succeed_on_view_with_queries_limit_skip...*failed* in function chttpd_view_test:'-should_succeed_on_view_with_queries_limit_skip/1-fun-4-'/1 (test/eunit/chttpd_view_test.erl, line 93) in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71) in call from eunit_proc:run_test/1 (eunit_proc.erl, line 510) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 335) in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 493) in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 435) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 325) in call from eunit_proc:run_group/2 (eunit_proc.erl, line 549) **error:{badmatch,{error,req_timedout}} output:<<"">> chttpd_view_test:108: should_succeed_on_view_with_multiple_queries...*failed* in function chttpd_view_test:'-should_succeed_on_view_with_multiple_queries/1-fun-5-'/1 (test/eunit/chttpd_view_test.erl, line 110) in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71) in call from eunit_proc:run_test/1 (eunit_proc.erl, line 510) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 335) in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 493) in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 435) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 325) in call from eunit_proc:run_group/2 (eunit_proc.erl, line 549) **error:{badmatch,{error,req_timedout}} output:<<"">> Is this critical > On 14. Feb 2020, at 15:45, Andy Wenk <andr...@family-wenk.de> wrote: > >> >> On 14. Feb 2020, at 12:27, Jan Lehnardt <j...@apache.org> wrote: >> >> >> >>> On 14. Feb 2020, at 12:22, Andy Wenk <andyw...@apache.org> wrote: >>> >>> I am on Mac OS Catalina and have the following problem: >>> >>> sha256sum --check apache-couchdb-*.tar.gz.sha256 >>> sha256sum: apache-couchdb-3.0.0-RC1.tar.gz.sha256: no properly >>> formatted SHA256 checksum lines found >>> >> >> if you edit the checksum file and add the filename, the --check option >> works, or you run without --check and compare the hashes manually. >> >> For the release I suggest we fix the checksum files of course :) > > ah see … I wrote a script for the process and I just pasted > apache-couchdb-*.tar.gz.sha256 in it … with using the whole filename and not > using —check it is fixed. > > Thanks Jan! > > All the best > > Andy > >> >> Best >> Jan >> — >> >>> I installed coreutils vi brew >>> >>> Andy ideo on this? >>> >>> All the best >>> >>> Andy >>> -- >>> Andy Wenk >>> Hamburg >>> >>> GPG fingerprint C32E 275F BCF3 9DF6 4E55 21BD 45D3 5653 77F9 3D29 >>> >>> >>> >>>> On 13. Feb 2020, at 21:43, rnew...@apache.org wrote: >>>> >>>> +1 >>>> >>>> MacOS 10.15.3 (ulimit -n 10000) >>>> >>>> Checksums and sig match >>>> make check passes cleanly >>>> >>>> >>>>> On 13 Feb 2020, at 17:55, Jan Lehnardt <j...@apache.org> wrote: >>>>> >>>>>> >>>>>> On 13. Feb 2020, at 17:56, Joan Touzet <woh...@apache.org> wrote: >>>>>> >>>>>> With this vote, we are now at 3 +1 PMC votes - a minimum for releasing. >>>>>> >>>>>> Everyone - please keep testing and submitting your experience. It'd be >>>>>> nice if someone could double check the GPG signing and checksums as >>>>>> well. If we need to stop the release, we will. >>>>> >>>>> I have checked all signatures to be fine. >>>>> >>>>>> >>>>>> Our typical policy is to release on Tuesdays for widest publicity. As >>>>>> Monday is a public holiday in Canada, I suggest we push things out one >>>>>> day. That'd put us on the following schedule, since we must wait 24 >>>>>> hours for the Apache mirrors to catch up: >>>>>> >>>>>> Tue Feb 18 - Push apache-couchdb-3.0.0.tar.gz* to dist.apache.org >>>>>> - Push Mac/Win binaries wherever they are going >>>>>> - Push binary packages to bintray.org >>>>>> - Test and merge 3.0.0 Docker PR >>>>>> - Push new Docker image to apache/couchdb >>>>>> >>>>>> Wed Feb 19 - Update couchdb.apache.org website >>>>>> - Announce widely (twitter, blog, announce@a.o, etc.) >>>>>> - Open downstream Docker PR for top-level couchdb image >>>>>> >>>>>> Any objections? >>>>> >>>>> None. >>>>> >>>>> Best >>>>> Jan >>>>> — >>>>>> >>>>>> -Joan "break me off a piece of that Kit Kat bar" Touzet >>>>>> >>>>>> On 2020-02-13 8:11, Jan Lehnardt wrote: >>>>>>> +1 >>>>>>> Checked on Mac OS Mojave. >>>>>>>> On 10. Feb 2020, at 17:33, Joan Touzet <woh...@apache.org> wrote: >>>>>>>> >>>>>>>> Dear community, >>>>>>>> >>>>>>>> I would like to propose that we release Apache CouchDB 3.0.0. >>>>>>>> >>>>>>>> Candidate release notes: >>>>>>>> >>>>>>>> https://docs.couchdb.org/en/latest/whatsnew/3.0.html >>>>>>>> >>>>>>>> We encourage the whole community to download and test these release >>>>>>>> artefacts so that any critical issues can be resolved before the >>>>>>>> release is made. Everyone is free to vote on this release, so dig >>>>>>>> right in! (Only PMC members have binding votes, but they depend on >>>>>>>> community feedback to gauge if an official release is ready to be >>>>>>>> made.) >>>>>>>> >>>>>>>> The release artefacts we are voting on are available here: >>>>>>>> >>>>>>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.0.0/rc.1 >>>>>>>> >>>>>>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512 >>>>>>>> checksums. >>>>>>>> >>>>>>>> Please follow the test procedure here: >>>>>>>> >>>>>>>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release >>>>>>>> >>>>>>>> Please remember that "RC1" is an annotation. If the vote passes, these >>>>>>>> artefacts will be released as Apache CouchDB 3.0.0. >>>>>>>> >>>>>>>> Please cast your votes now. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Joan "once in a lifetime" Touzet >>>>> >>>>> -- >>>>> Professional Support for Apache CouchDB: >>>>> https://neighbourhood.ie/couchdb-support/