All the tests reported as failing to me.
When I ran with -d, I see this in the transcript:
(:RESULT :TYPE "International Allegro CL Enterprise Edition" :VERSION "8.2 [64-bit Mac OS X (Intel)] (Oct 1, 2012 17:20)" :FILE #P"/Users/rpg/lisp/asdf/build/results/alisp-pathnames.txt" :SYSTEM-FAILURES (0 320) :DIRECTORY-FAILURES (0 1280) :FILE-FAILURES (0 1920) :HOMOGENEOUS 0) Script succeeded and then I drop out of the script, after having run only 1 test.
So I'm wondering if there's something wrong in the way the test results are accumulated by the script..
Cheers, r
On Sun, Jan 13, 2013 at 10:07 PM, Robert Goldman rpgoldman@sift.info wrote:
All the tests reported as failing to me.
I was trying to close the *standard-input* during batch processing, with the hope that it would help Lisps die cleaner and better when running in batch mode instead of dropping to a debugger, but apparently, Allegro and ECL at least *really* hate that. So I don't try anymore.
So I'm wondering if there's something wrong in the way the test results are accumulated by the script..
On the other hand, I moved the output of the asdf-pathname-test script from build/output.txt to where the other test outputs are: build/results/allegro-pathnames.txt
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org We have actually contrived to invent a new kind of hypocrite. The old hypocrite, Tartuffe or Pecksniff, was a man whose aims were really worldly and practical, while he pretended that they were religious. The new hypocrite is one whose aims are really religious, while he pretends that they are worldly and practical. — G. K. Chesterton
-
Faré -
Robert Goldman