On 2/25/13 Feb 25 -9:26 AM, Faré wrote:
On Mon, Feb 25, 2013 at 10:20 AM, Robert Goldman rpgoldman@sift.info wrote:
On 2/24/13 Feb 24 -11:16 PM, Faré wrote: ....
re: test-encodings
Uh, doesn't this test print the test name just before, in the logs?
It prints the test name, but my stuff adds a sub-test name. There were, IIRC, three places where we check UTF-8 encoding of the lambda character.
I made them distinguishable, but in a kludgy way. See attached patch. Could tidy it up, but possibly not worth it. LMK what you think.
Wait, in with-encoding-test, there is a (format t "~&Test ~A: should be ~A~%" ',sys ',encoding) that ought to tell you which subtest it is already.
Are you providing more information?
Possibly not.
But when I look for "should be" in my test output file, it is many lines away from the failure message.
See attached transcript.... There's a pile of garbage about jar file loading between the output of that format line and the message about the test failing. That format output is 24 lines away from:
TEST ABORTED: On test Encoding test EXPLICIT-U8. These two expressions fail comparison with EQUAL: (STRING-CHAR-CODES "λ") evaluates to (338 170) (EXPECTED-CHAR-CODES (QUOTE :UTF-8)) evaluates to (955)
cheers, r