Oh, I see. Yes, indeed, the whole test suite was broken. I've pushed fixes for it and for the things that weren't caught by the old test suite.
Thanks, Robby On Sun, Jul 17, 2011 at 8:27 AM, Casey Klein <clkl...@eecs.northwestern.edu> wrote: > Here's what I tried: > > 1. I added this test, which should fail for identifying the wrong party: > > (test/neg-blame > 'contract-arrow-wrong-number-values > '((contract (-> integer? (values integer? integer?)) > (lambda (x) (values 1)) > 'pos > 'neg) > 1)) > > 2. From the directory containing contract-test.rktl, I ran: > > $ racket > Welcome to Racket v5.1.2.3. >> (load "contract-test.rktl") > > and got this message: > > Passed all tests. > (Other messages report successful tests of error-handling behavior.) > > Those other messages contain this output for the new test: > > testing: contract-arrow-wrong-number-values > ((contract (-> integer? (values integer? integer?)) (lambda (x) > (values 1)) (quote pos) (quote neg)) 1) =e=> exception raised by > exception handler: test/spec-failed: unknown blame name "neg"; > original exception raised: self-contract violation: expected 2 values, > returned 1 value > contract from: pos, blaming: pos > contract: > (-> integer? (values integer? integer?)) > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
