Some unit tests currently failing
As a sanity check before trying to make some changes in iterate
I tried to run the unit tests in a fresh clone of the repo. It looks to me as if there are several failures, though the wording is a bit ambiguous. I ran the tests with make test
which I believe ran SBCL 2.4.0 on my Ubuntu 22.04.3 LTS box, using the version of RT that comes for free with SBCL. At the end of its output it appeared to report
6 out of 278 total tests failed: ITERATE.TEST::ALWAYS.FINALLY,
ITERATE.TEST::NEVER.FINALLY, ITERATE.TEST::THEREIS.FINALLY,
ITERATE.TEST::IN-STREAM.2, ITERATE.TEST::BUG/WALK.2,
ITERATE.TEST::BUG/COLLECT-AT-BEGINNING.
No unexpected failures.
DO-ITERATE-TESTS ran successfully.
; in:
; PROGN (FORMAT *ERROR-OUTPUT* "~&Note: These tests generate warnings ~
; involving MACROLET within Iterate~%")
; (ITERATE:MULTIPLYING (ITERATE.TEST::FOO))
;
; caught STYLE-WARNING:
; undefined function: ITERATE:MULTIPLYING
;
; compilation unit finished
; Undefined function:
; ITERATE:MULTIPLYING
; caught 1 ERROR condition
; caught 1 WARNING condition
; caught 1 STYLE-WARNING condition
I'm not quite sure how to interpret that "No unexpected failures." Is that RT-speak for "no failures outside the stuff being tested," or "the above failures are known and expected," or something else?
Anyway, would it have been expected that some tests fail, or is this an indication that there's something screwy in my configuration I need to look into? Are these actual bugs in the version of iterate in the repo that need addressing?