Today Erik configured for me a VM on his server, where I can run cl-test-grid tests.
We were trying the recent ABCL trunk (1.2.0-dev-svn-14436) on the very very recent quicklisp 2013-03-12, which includes long awaited releases for closer-mop and cffi with ABCL patches.
Some notes I collected:
1. New CFFI tries to (require :jss) and fails, because (require :abcl-contrib) hasn't been done. If we do (require :abcl-contrib) then CFFI loads. 2. But when we test actual work, for example by doing (ql:quickload :drakma) (drakma:http-request "https://google.com/") it fails with strange error "UNDEFINED-FUNCTION is called". On SBCL these calls work. 3. (ql:quickload "cl-l10n") fails with ArrayIndexOutOfBounds - may be an ABCL bug.
Aside from this, closer-mop seems working (at leas compilation of dependent library "access" doesn't fail anymore).
Mark, If you want to quickly reproduce the above problems, you can access the server at cl-test-grid.cloud.efficito.com. Username - testgrid. Erik have added your ssh public key from common-lisp.net to that server.
To start ABCL you can use
rlwrap java -jar ~/lisps/abcl/dist/abcl.jar (ql:quickload :cl-l10n) => ERROR: java.lang.ArrayIndexOutOfBoundsException: 0
Before starting cl-test-grid tests, I would like to understand, should cl-test-grid always pass --eval "(require :abcl-contrib)" parameter to ABCL when starting it to run a test?
Previously cl-test-grid only tested pure ABCL, without contribs.
Feedback on this question is very welcome.
Best regards, - Anton
On 3/16/13 11:40 PM, Anton Vodonosov wrote:
Today Erik configured for me a VM on his server, where I can run cl-test-grid tests.
We were trying the recent ABCL trunk (1.2.0-dev-svn-14436) on the very very recent quicklisp 2013-03-12, which includes long awaited releases for closer-mop and cffi with ABCL patches.
Some notes I collected:
- New CFFI tries to (require :jss) and fails, because (require :abcl-contrib) hasn't been done. If we do (require :abcl-contrib) then CFFI loads.
My use of the EVAL-WHEN form that wraps the (REQUIRE :JSS) is entirely bogus from what I can tell. I will get a change into CFFI soon, hopefully tomorrow, but getting another CFFI release will probably take a long time.
- But when we test actual work, for example by doing (ql:quickload :drakma) (drakma:http-request "https://google.com/") it fails with strange error "UNDEFINED-FUNCTION is called". On SBCL these calls work.
This has worked for me in the past from what I remember. DRAKMA has to use CL+SSL for the "https" scheme, so maybe there is a bad interaction with the OpenSSL libraries.
[…]
Mark, If you want to quickly reproduce the above problems, you can access the server at cl-test-grid.cloud.efficito.com. Username - testgrid. Erik have added your ssh public key from common-lisp.net to that server.
To start ABCL you can use
rlwrap java -jar ~/lisps/abcl/dist/abcl.jar (ql:quickload :cl-l10n) => ERROR: java.lang.ArrayIndexOutOfBoundsException: 0
Thanks for setting me up: I'll take advantage of the courtesy in the next day or so, reporting back.
Before starting cl-test-grid tests, I would like to understand, should cl-test-grid always pass --eval "(require :abcl-contrib)" parameter to ABCL when starting it to run a test?
Yes, please do this to get beyond the CFFI problem you have found.
Previously cl-test-grid only tested pure ABCL, without contribs.
I don't expect that the (REQUIRE :ABCL-CONTRIB) will take too much additional time. It will, of course, mask other failures to correctly load things like you have discovered in cffi-0.11.0.
On 17-03-2013 20:40, Mark Evenson wrote:
My use of the EVAL-WHEN form that wraps the (REQUIRE :JSS) is entirely bogus from what I can tell. I will get a change into CFFI soon, hopefully tomorrow, but getting another CFFI release will probably take a long time.
Maybe not. Such a simple bugfix release should be pretty quick!
On Mar 18, 2013, at 1218 , Luís Oliveira luismbo@gmail.com wrote:
On 17-03-2013 20:40, Mark Evenson wrote:
My use of the EVAL-WHEN form that wraps the (REQUIRE :JSS) is entirely bogus from what I can tell. I will get a change into CFFI soon, hopefully tomorrow, but getting another CFFI release will probably take a long time.
Maybe not. Such a simple bugfix release should be pretty quick!
I've created a [github pull request][1] which fixes this problem.
[1]: https://github.com/cffi/cffi/pull/23
-- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."
armedbear-devel@common-lisp.net