I think that must be using an older version of iterate, in quicklisp, because the latest version has `iterate/tests` instead (as it should).
Best, r
On 24 Jan 2018, at 17:12, Patrick Stein wrote:
I was going to recommend referring to cl-test-grid, but it seems that testgrid cannot locate the iterate-tests system.
https://common-lisp.net/project/cl-test-grid/library/iterate.html
-- Patrick pat@nklein.com
On Jan 24, 2018, at 4:38 PM, Robert Goldman rpgoldman@sift.info wrote:
On 24 Jan 2018, at 16:17, Ilya Perminov wrote:
I think the warings are expected. A note just above them says "Note: These tests generate warnings involving MACROLET within Iterate". I am not sure why our test results are different. Maybe my SBCL version is too old, I'll try the latest one.
Looks like these 5 failures are what I should be expecting. At the top of iterate-test.lisp I find this:
;; This is here to document which tests are failing at the time of ;; writing. It's not used directly here, but the tests of the ;; iterate-compat package of hu.dwim.reiterate expect it. (defvar *tests-expected-to-fail* '(always.finally never.finally thereis.finally bug/walk.2 bug/collect-at-beginning )) That suggests that the errors in code-movement.finally, code-movement.finally-protected and code-movement.else are unique to ACL and are not expected to fail.
I'll try to make time to have a look at what is going on there.
Best, r