In cl-test-grid project we are running tests of CL libraries on various lisps implementation and OSes. The tests include ql:quickload for every ASDF system in quicklisp and also running testsuites of some libraries.
When we do (ql:quickload :ningle-test) it runs the testsuite, including starting hunchentoot.
It sometimes fails due to port being busy and just hangs on some lisps.
For example, sbcl --eval "(ql:quickload :ningle-test)" --eval "(quit)" hangs forever.
Is it possible to separate the test running from system loading?
I.e. to run testsuite on could do
common-lisp (ql:quickload :ningle-test) (ningle-test:run-tests)
But if you just want to load ASDF system you can (ql:quickload :ningle-test)
Hi.
In cl-test-grid project we are running tests of CL libraries on various lisps implementation and OSes. The tests include ql:quickload for every ASDF system in quicklisp and also running testsuites of some libraries.
You may find your library test results at http://common-lisp.net/project/cl-test-grid/library/[LIBNAME].html. For example http://common-lisp.net/project/cl-test-grid/library/ningle.html
When we do (ql:quickload :ningle-test) it runs the testsuite, including starting hunchentoot. It sometimes fails due to port being busy and just hangs on some lisps.
For example,
sbcl --eval "(ql:quickload :ningle-test)" --eval "(quit)"hangs forever.Is it possible to separate the test running from system loading? I.e. to run testsuite on could do
common-lisp (ql:quickload :ningle-test) (ningle-test:run-tests)But if you just want to load ASDF system you can(ql:quickload :ningle-test)