[asdf-devel] Ready to release?

I tweaked the upgrade to punt more on abcl, and it looks like it's working. cmucl, on the other hand, is desperately borking on upgrade, with or without punt. Apart from that, asdf 3.0.2.28 passes all tests for me on linux, including upgrade tests (except on cmucl), for ccl clisp sbcl cmucl allegro allegromodern abcl I also ran tests (but not upgrade tests yet) successfully for: ecl ecl_bytecodes lispworks xcl A few minor patches ago, I also tested that it can be compiled and run correctly on genera. I admit I'm growing impatient for a release 3.0.3 of ASDF. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability

Results on Windows for 3.0.2.28: ========================== SBCL 1.1.12: 48 tests pass, 0 fail CCL 1.10-dev: 48 tests pass, 0 fail CCL 1.9-r15764: 46 tests pass, 2 fail (failing tests: test-bundle.script test-run-program.script) Allegro CL 9.0 mlisp: 48 tests pass, 0 fail Allegro CL 9.0 alisp: 48 tests pass, 0 fail Allegro CL 9.0 mlisp8: 47 tests pass, 1 fail (failing test: test-utilities.script) Also: Makefile:126: recipe for target `test-lisp' failed. Allegro CL 9.0 alisp8: 46 tests pass, 2 fail (failing tests: test-encodings.script, test-utilities.script) allegro.text and allegromodern.text attached (for the alisp8 and mlisp8) Regards, Dave On Thu, Oct 17, 2013 at 1:37 PM, Faré <fahree@gmail.com> wrote:
I tweaked the upgrade to punt more on abcl, and it looks like it's working. cmucl, on the other hand, is desperately borking on upgrade, with or without punt.
Apart from that, asdf 3.0.2.28 passes all tests for me on linux, including upgrade tests (except on cmucl), for ccl clisp sbcl cmucl allegro allegromodern abcl
I also ran tests (but not upgrade tests yet) successfully for: ecl ecl_bytecodes lispworks xcl
A few minor patches ago, I also tested that it can be compiled and run correctly on genera.
I admit I'm growing impatient for a release 3.0.3 of ASDF.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability
-- My Best, Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

Dear Dave, unhappily, Allegro Express doesn't come with alisp8 or mlisp8, and there is no useful output (because of +c ?) in your Windows logs. I suspect that the errors are due to the base-char vs non-base-char issues in test-utilities in test-encodings. There is a slight chance of bug in UIOP's handling of the string hierarchy (are there intermediate types between base-char and character? between base-string and string?), and probably the right thing to do is to find some combination of features based on which to disable some tests. So, you're on your own there, although someone else with a full allegro license (not necessarily on Windows) might help. But it should be simple. In any case, this should be a release blocker. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Maybe Jesus was right when he said that the meek shall inherit the earth — but they inherit very small plots, about six feet by three. — Robert Heinlein, "Time Enough For Love" On Thu, Oct 17, 2013 at 2:33 PM, Dave Cooper <david.cooper@genworks.com> wrote:
Results on Windows for 3.0.2.28: ==========================
SBCL 1.1.12: 48 tests pass, 0 fail
CCL 1.10-dev: 48 tests pass, 0 fail
CCL 1.9-r15764: 46 tests pass, 2 fail (failing tests: test-bundle.script test-run-program.script)
Allegro CL 9.0 mlisp: 48 tests pass, 0 fail
Allegro CL 9.0 alisp: 48 tests pass, 0 fail
Allegro CL 9.0 mlisp8: 47 tests pass, 1 fail (failing test: test-utilities.script) Also: Makefile:126: recipe for target `test-lisp' failed.
Allegro CL 9.0 alisp8: 46 tests pass, 2 fail (failing tests: test-encodings.script, test-utilities.script)
allegro.text and allegromodern.text attached (for the alisp8 and mlisp8)
Regards,
Dave
On Thu, Oct 17, 2013 at 1:37 PM, Faré <fahree@gmail.com> wrote:
I tweaked the upgrade to punt more on abcl, and it looks like it's working. cmucl, on the other hand, is desperately borking on upgrade, with or without punt.
Apart from that, asdf 3.0.2.28 passes all tests for me on linux, including upgrade tests (except on cmucl), for ccl clisp sbcl cmucl allegro allegromodern abcl
I also ran tests (but not upgrade tests yet) successfully for: ecl ecl_bytecodes lispworks xcl
A few minor patches ago, I also tested that it can be compiled and run correctly on genera.
I admit I'm growing impatient for a release 3.0.3 of ASDF.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

I was able to reproduce the test-utilities.script failure on alisp8 and mlisp8 on Linux, with more output going into the logs (attached). I'll send the output from test-encodings.script on Windows separately (this does not appear to be failing on Linux). On Thu, Oct 17, 2013 at 3:03 PM, Faré <fahree@gmail.com> wrote:
Dear Dave,
unhappily, Allegro Express doesn't come with alisp8 or mlisp8, and there is no useful output (because of +c ?) in your Windows logs. I suspect that the errors are due to the base-char vs non-base-char issues in test-utilities in test-encodings. There is a slight chance of bug in UIOP's handling of the string hierarchy (are there intermediate types between base-char and character? between base-string and string?), and probably the right thing to do is to find some combination of features based on which to disable some tests.
So, you're on your own there, although someone else with a full allegro license (not necessarily on Windows) might help. But it should be simple. In any case, this should be a release blocker.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Maybe Jesus was right when he said that the meek shall inherit the earth — but they inherit very small plots, about six feet by three. — Robert Heinlein, "Time Enough For Love"
On Thu, Oct 17, 2013 at 2:33 PM, Dave Cooper <david.cooper@genworks.com> wrote:
Results on Windows for 3.0.2.28: ==========================
SBCL 1.1.12: 48 tests pass, 0 fail
CCL 1.10-dev: 48 tests pass, 0 fail
CCL 1.9-r15764: 46 tests pass, 2 fail (failing tests: test-bundle.script test-run-program.script)
Allegro CL 9.0 mlisp: 48 tests pass, 0 fail
Allegro CL 9.0 alisp: 48 tests pass, 0 fail
Allegro CL 9.0 mlisp8: 47 tests pass, 1 fail (failing test: test-utilities.script) Also: Makefile:126: recipe for target `test-lisp' failed.
Allegro CL 9.0 alisp8: 46 tests pass, 2 fail (failing tests: test-encodings.script, test-utilities.script)
allegro.text and allegromodern.text attached (for the alisp8 and mlisp8)
Regards,
Dave
On Thu, Oct 17, 2013 at 1:37 PM, Faré <fahree@gmail.com> wrote:
I tweaked the upgrade to punt more on abcl, and it looks like it's working. cmucl, on the other hand, is desperately borking on upgrade, with or without punt.
Apart from that, asdf 3.0.2.28 passes all tests for me on linux, including upgrade tests (except on cmucl), for ccl clisp sbcl cmucl allegro allegromodern abcl
I also ran tests (but not upgrade tests yet) successfully for: ecl ecl_bytecodes lispworks xcl
A few minor patches ago, I also tested that it can be compiled and run correctly on genera.
I admit I'm growing impatient for a release 3.0.3 of ASDF.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699
-- My Best, Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

On Thu, Oct 17, 2013 at 3:20 PM, Dave Cooper <david.cooper@genworks.com> wrote:
I'll send the output from test-encodings.script on Windows separately (this does not appear to be failing on Linux).
Is it saying that (typep (code-char (1- char-code-limit)) (quote base-char)) ;==> NIL yet (typep (code-char (1- char-code-limit)) (quote character)) ;==> T and (subtypep 'character 'base-char) ;==> T T ? If so, there's a clear bug in alisp8 and mlisp8. If not, I'm missing something about the code. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The last ten percent of any reform is the most difficult to achieve. Moreover, it is often harmful. — John McCarthy

On Thu, Oct 17, 2013 at 3:27 PM, Faré <fahree@gmail.com> wrote:
Is it saying that (typep (code-char (1- char-code-limit)) (quote base-char)) ;==> NIL yet (typep (code-char (1- char-code-limit)) (quote character)) ;==> T and (subtypep 'character 'base-char) ;==> T T ?
GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) NIL GDL-USER> (subtypep 'character 'base-char) T T By the way, I am not able to reproduce the test-encodings.script failure on alisp8.exe and mlisp8.exe - I ran them several more times and they are passing now. -- My Best, Dave Cooper, Genworks Support

To be clear, on alisp8, we have: GDL-USER> (uiop:featurep :ics) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) NIL GDL-USER> (subtypep 'character 'base-char) T T ... and on alisp, we have: GDL-USER> (uiop:featurep :ics) T GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) T GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) T GDL-USER> (subtypep 'character 'base-char) T T On Thu, Oct 17, 2013 at 4:00 PM, Dave Cooper <david.cooper@genworks.com>wrote:
On Thu, Oct 17, 2013 at 3:27 PM, Faré <fahree@gmail.com> wrote:
Is it saying that (typep (code-char (1- char-code-limit)) (quote base-char)) ;==> NIL yet (typep (code-char (1- char-code-limit)) (quote character)) ;==> T and (subtypep 'character 'base-char) ;==> T T ?
GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) NIL GDL-USER> (subtypep 'character 'base-char) T T
By the way, I am not able to reproduce the test-encodings.script failure on alisp8.exe and mlisp8.exe - I ran them several more times and they are passing now.
-- My Best,
Dave Cooper, Genworks Support
-- My Best, Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

And for the record, what are char-code-limit (code-char (1- char-code-limit)) ? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If it's not worth doing, it's not worth doing well — Donald Hebb If it's not worth doing right, it's not worth doing. — Scott McKay On Thu, Oct 17, 2013 at 4:06 PM, Dave Cooper <david.cooper@genworks.com> wrote:
To be clear, on alisp8, we have:
GDL-USER> (uiop:featurep :ics) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) NIL GDL-USER> (subtypep 'character 'base-char) T T
... and on alisp, we have:
GDL-USER> (uiop:featurep :ics) T GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) T GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) T GDL-USER> (subtypep 'character 'base-char) T T
On Thu, Oct 17, 2013 at 4:00 PM, Dave Cooper <david.cooper@genworks.com> wrote:
On Thu, Oct 17, 2013 at 3:27 PM, Faré <fahree@gmail.com> wrote:
Is it saying that (typep (code-char (1- char-code-limit)) (quote base-char)) ;==> NIL yet (typep (code-char (1- char-code-limit)) (quote character)) ;==> T and (subtypep 'character 'base-char) ;==> T T ?
GDL-USER> (typep (code-char (1- char-code-limit)) (quote base-char)) NIL GDL-USER> (typep (code-char (1- char-code-limit)) (quote character)) NIL GDL-USER> (subtypep 'character 'base-char) T T
By the way, I am not able to reproduce the test-encodings.script failure on alisp8.exe and mlisp8.exe - I ran them several more times and they are passing now.
-- My Best,
Dave Cooper, Genworks Support
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

On Thu, Oct 17, 2013 at 4:08 PM, Faré <fahree@gmail.com> wrote:
And for the record, what are char-code-limit (code-char (1- char-code-limit)) ?
alisp8: GDL-USER> (uiop:featurep :ics) NIL GDL-USER> char-code-limit 65536 GDL-USER> (code-char (1- char-code-limit)) NIL alisp: GDL-USER> (uiop:featurep :ics) T GDL-USER> char-code-limit 65536 GDL-USER> (code-char (1- char-code-limit)) #\ [as seen after being copy/pasted from emacs in a Linux VM to Google Chrome on Mac] #\��� [as seen after being copy/pasted from terminal window in a Linux VM to Google Chrome on Mac] [it shows up as the three inverse-video question marks when seen in the Terminal, and as #\ with a single empty box when seen in Emacs] -- My Best, Dave Cooper, Genworks Support

alisp8:
GDL-USER> (uiop:featurep :ics) NIL GDL-USER> char-code-limit 65536 GDL-USER> (code-char (1- char-code-limit)) NIL
This smells like a bug, and I filed a bug report to franz, and pushed a workaround to test-utilities.script. Do you have a transcript for the remaining failure with test-encodings on mlisp8 or such? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The greatest lies always come in a thin coating of truth.

On Thu, Oct 17, 2013 at 4:41 PM, Faré <fahree@gmail.com> wrote:
Do you have a transcript for the remaining failure with test-encodings on mlisp8 or such?
I don't. I re-ran the tests a few times and could not reproduce the failure. I'll run everything from the top with a fresh build/ directory a bit later, with your test-utilities.script workaround, and see if any of the failures pop up again.
participants (2)
-
Dave Cooper
-
Faré