Re: ttn-pers-scheme 0.48 available

[Thien-Thi Nguyen]

() "Issac Trotts" <address@hidden>
() Mon, 9 Apr 2007 15:06:33 -0700

   FAIL: call-process.test: ls zzzzz.zzz (sep args)
   FAIL: call-process.test: ls zzzzz.zzz (sep args) #:norm #t
   FAIL: call-process.test: ls zzzzz.zzz #:norm #t

here are the failing tests from tests/call-process.test, instrumented to
show the return value of `call-process'.

(pass-if "ls zzzzz.zzz (sep args)" (= 256 (call-process/DEBUG "ls" "zzzzz.zzz" 
#:errp #f)))
(pass-if "ls zzzzz.zzz (sep args) #:norm #t" (= 256 (call-process/DEBUG "ls" 
"zzzzz.zzz" #:norm #t #:errp #f)))
(pass-if "ls zzzzz.zzz #:norm #t" (= 256 (call-process/DEBUG "ls zzzzz.zzz" 
#:norm #t #:errp #f)))

they now call `call-process/DEBUG', which you have to add before the
tests (most anywhere at top-level is fine, as long as it's before):

(define (call-process/DEBUG . args)
  (let ((rv (apply call-process args)))
    (simple-format #t "HEY: rv => ~A  (status:exit-val rv) => ~A\n"
                   rv (status:exit-val rv))
    rv
    ;;(status:exit-val rv)
    ))

could you make these modifications, re-run "make check" and let me know
what you see?  if `rv' is wrong, but (status:exit-val rv) is right, that
means i have update the tests and you can ignore the errors (or comment
out the alternative return value to get the tests to pass).  if neither
of them is right, i have to think some more... hmmm...

   FAIL: call-process-to-buffers.test: check-cp->b ls
   FAIL: call-process-to-buffers.test: check-cp->b ls
   FAIL: call-process-to-buffers.test: check-cp->b ls zzzzz.zzz

i suspect these failures are related to the ones above (we can look at
these after we figure out the first three).

thi