You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the fresh quicklisp client (quicklisp:quickload :cl-base64-tests) fails, but (quicklisp:quickload :cl-base64) works.
Few days ago it worked (although with another less critical problem, which I'll report later).
The same story with :iterate - (quicklisp:quickload :iterate-tests) fails while (quicklisp:quickload :iterate) works.
What is common between these libraries is that the -tests system is defined the same .asd file as the main system
(i.g. :cl-base64-tests is defined in :cl-base64.asd).
The text was updated successfully, but these errors were encountered:
I've changed how things work so you cannot attempt to load a system that does not have its own system file until it has been defined by loading the defining system file. Just like how ASDF works.
With the fresh quicklisp client (quicklisp:quickload :cl-base64-tests) fails, but (quicklisp:quickload :cl-base64) works.
Few days ago it worked (although with another less critical problem, which I'll report later).
The same story with :iterate - (quicklisp:quickload :iterate-tests) fails while (quicklisp:quickload :iterate) works.
What is common between these libraries is that the -tests system is defined the same .asd file as the main system
(i.g. :cl-base64-tests is defined in :cl-base64.asd).
The text was updated successfully, but these errors were encountered: