> I ran the above, and it seemed to work well, until I got to the > "conform.rkt" test, when it spewed a *lot* of output like this: > > _62969@http://localhost:8371/eval:4681 > _63082@http://localhost:8371/eval:2199 > _63901@http://localhost:8371/eval:6925 > _63932@http://localhost:8371/eval:6052 > _63900@http://localhost:8371/eval:6625 > _63899@http://localhost:8371/eval:6945 > _63080@http://localhost:8371/eval:4579 > _62961@http://localhost:8371/eval:4702
Huh; no idea what's going on there yet. that looks like a stack trace coming out of JavaScript land. That shouldn't be right. What browser was it running under? Are your patches on master or release now? I'll go ahead and check to see if I can replicate the stack trace you're seeing. _________________________ Racket Developers list: http://lists.racket-lang.org/dev
