[GitHub] [couchdb] nickva commented on issue #4259: make check failed in arm64
nickva commented on issue #4259: URL: https://github.com/apache/couchdb/issues/4259#issuecomment-1396062541 @Tom-python0121 sorry for the delayed response. It looks like there is some exception throw. The eunit (the test framework used to run the tests) dumps extra logs in `src/$app/.eunit/couch.log`. In this case it looks like it might be `src/chttpd/.eunit/couch.log`. See if there are any errors or exception there? Since it involves view tests I suspect the spidermonkey (couch js runtime) might not linked or built properly. To run just one test module could try: ``` $ make && make eunit apps=chttpd suites=chttpd_view_test $ cat src/chttpd/.eunit/couch.log ``` req_timedout might also have sometime to do with network or socket setup not working properly and either the server unable to bind to a socket to listen or the test client from reaching the server. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [couchdb] nickva commented on issue #4259: make check failed in arm64
nickva commented on issue #4259: URL: https://github.com/apache/couchdb/issues/4259#issuecomment-1366432910 > I downloaded it from this URL, isn't it? Are there any other URLs? > > ``` > wget https://github.com/apache/couchdb/archive/refs/tags/3.3.0-RC2.tar.gz > [root@bigdata spack-stage-couchdb-3.3.0-RC2-pp6mytoamrlxeaykdrgpytuslzbxyo63]# sha256sum 3.3.0-RC2.tar.gz > 0b823f7027c2ec18677d8fe4cc02977893579491763897d5fcc2696983c15eb6 3.3.0-RC2.tar.gz > ``` There is our answer. That's not the correct URL. That's the git tag but that's not our release candidate tar.gz file. That one is located at: https://dist.apache.org/repos/dist/dev/couchdb/source/3.3.0/rc.2 You can track the ML release vote thread as well: https://lists.apache.org/thread/rgrh1bctsosoxqfzf0xn7oc7x0b20x3k After the vote passes it will be tagged as 3.3.0 and but the release would then be available via a link at https://couchdb.apache.org/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [couchdb] nickva commented on issue #4259: make check failed in arm64
nickva commented on issue #4259: URL: https://github.com/apache/couchdb/issues/4259#issuecomment-1366427276 @Tom-python0121 exactly, it doesn't seem right that it's downloading and fetching rebar2 or rebar3. Those scripts should be in the the .tgz already. Just to double-check again wonder if we're looking at the same tgz file: ``` nickv@nvi:~/tmp $ cat apache-couchdb-3.3.0-RC2.tar.gz.sha256 e8c6bf3f99a8f0d2af5806652f57d53796367e2d4b24dedc86e268cf86f787a0 apache-couchdb-3.3.0-RC2.tar.gz nickv@nvi:~/tmp $ sha256sum -c apache-couchdb-3.3.0-RC2.tar.gz.sha256 apache-couchdb-3.3.0-RC2.tar.gz: OK nickv@nvi:~/tmp $ rm -rf apache-couchdb-3.3.0 nickv@nvi:~/tmp $ tar xfz apache-couchdb-3.3.0-RC2.tar.gz nickv@nvi:~/tmp $ ls -l apache-couchdb-3.3.0/bin total 1120 -rw-rw-r-- 1 nickv nickv 68 Dec 22 02:53 erlang-version.escript -rwxrwxr-x 1 nickv nickv 134844 Dec 22 03:00 erlfmt -rwxrwxr-x 1 nickv nickv 203550 Dec 22 03:00 rebar -rwxrwxr-x 1 nickv nickv 800215 Dec 22 03:00 rebar3 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [couchdb] nickva commented on issue #4259: make check failed in arm64
nickva commented on issue #4259:
URL: https://github.com/apache/couchdb/issues/4259#issuecomment-1366369747
@Tom-python0121 thanks for double checking.
When I run `./configure` from the tar.gz I get only:
```
$ ./configure
==> configuring couchdb in rel/couchdb.config
You have configured Apache CouchDB, time to relax. Relax.
```
But in your case it seems it's attempting to install rebar or rebar3. So it
could be one of these sections that's failing:
https://github.com/apache/couchdb/blob/f6ddbe24cace7a841508c451bc12820b9d76c218/configure#L307-L315
Wonder what your `${rootdir}` is in
https://github.com/apache/couchdb/blob/f6ddbe24cace7a841508c451bc12820b9d76c218/configure#L336-L338
and if bin/rebar3 found there. Would you be able to echo it in a debug line
with a patch like this:
```
if [ -z "${REBAR3}" ]; then
echo "rebar3 install **"
echo "rootdir = ${rootdir}"
install_local_rebar3
REBAR3=${rootdir}/bin/rebar3
fi
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [couchdb] nickva commented on issue #4259: make check failed in arm64
nickva commented on issue #4259: URL: https://github.com/apache/couchdb/issues/4259#issuecomment-1366094372 Based on what @big-r81 pointed out, it seems like it needs access to the network to install a few package. I wonder if you have access to the network in the environment @Tom-python0121? Is it the `./configure` or `make release` or `make check` step that fails? We just fixed a similar issues and but there is probably a few more instances of it left https://github.com/apache/couchdb/pull/4319 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
