Finished clisp on Linux, still the one failure for pathname, here is the -test.text and -pathnames.text:
https://www.dropbox.com/sh/jc2cqwpkp06dupm/Jmq7a3BhtZ/asdf-failures/3.1.0.26
Windows tests still running, results will be copied into windows/ folder at above location.
On Thu, Dec 19, 2013 at 4:29 PM, Faré fahree@gmail.com wrote:
On Thu, Dec 19, 2013 at 11:24 AM, Dave Cooper david.cooper@genworks.com wrote:
I had a couple failures: abcl/windows, clisp/windows, clisp/linux:
https://www.dropbox.com/sh/jc2cqwpkp06dupm/1IBEQ9XyKi/asdf-failures/3.1.0.24
OK, can you try the latest, 3.1.0.26, where undo a previous hack and punt for the ending space from cmd.exe's echo on Windows? It also has some test fixes for clisp on Linux as compared to 3.1.0.24.
Also, if you see asdf-pathname-test failures a the test report, can you attach the corresponding build/results/clisp-pathnames.text?
Thanks a lot for your patient testing!
I also updated the TODO and Changelog, and took the liberty of implementing that optimization I had been talking about: when upgrading from forward-compatible-enough version (i.e. 2.27 or later), have a softer upgrade that doesn't clear the defined system table or override some hook variables.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org man, n: a computer that can pass the Turing test. — Corey Sweeney