[asdf-devel] Testing with RMCL....
I am willing to run the ASDF tests using RMCL, since my Mac still has Snow Leopard, instead of Lion. *However*, as a non-RMCL user, I have no idea how to run it from the shell, so that we can run the test suite on RMCL. Can someone please offer me a clue? I can't be trying to run this from the GUI every time it needs a test. I had to give up testing LispWorks for the same reason. thanks, r
Sent from my iPad On 17 Apr 2012, at 21:36, Robert Goldman <rpgoldman@sift.info> wrote:
I am willing to run the ASDF tests using RMCL, since my Mac still has Snow Leopard, instead of Lion.
*However*, as a non-RMCL user, I have no idea how to run it from the shell, so that we can run the test suite on RMCL.
Can someone please offer me a clue?
You can't run RMCL from a shell...
I can't be trying to run this from the GUI every time it needs a test. I had to give up testing LispWorks for the same reason.
...but you can run LispWorks from a shell. Pascal
thanks, r
_______________________________________________ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On 4/18/12 Apr 18 -12:10 AM, Pascal Costanza wrote:
On 17 Apr 2012, at 21:36, Robert Goldman <rpgoldman@sift.info> wrote:
I am willing to run the ASDF tests using RMCL, since my Mac still has Snow Leopard, instead of Lion.
*However*, as a non-RMCL user, I have no idea how to run it from the shell, so that we can run the test suite on RMCL.
Can someone please offer me a clue?
You can't run RMCL from a shell...
Hm. Well then I cannot run the tests there. Maybe someone who is dedicated to seeing RMCL + ASDF continue to work would be so kind as to provide a technique for running the tests. This may be quite tricky, since the tests require restarting lisp in pristine state. Question: is it possible to control RMCL using applescript? I suppose that could be used to perform the functions for which we are currently using shell scripts. An ongoing rewrite effort to get the tests to work is likely to be quite laborious. Given that we cannot test on RMCL, and it's EOLed by the release of Lion, I am inclined to say we should end official ASDF support for RMCL. Incorporating patches to keep ASDF working on RMCL seems fine, but I don't believe that we can continue to fix problems on that platform ourselves.
I can't be trying to run this from the GUI every time it needs a test. I had to give up testing LispWorks for the same reason.
...but you can run LispWorks from a shell.
Actually, you can run LispWorks from a shell, but only if you can dump an image, which is a privilege limited to those who have a full (paid) license. I don't have such a license, so I cannot run the LispWorks tests. It would be nice if someone from the community (someone working for LispWorks, perhaps) would take the responsibility of verifying that ASDF releases run on LW. I don't believe Faré can do this, either. Best, Robert
Pascal
thanks, r
_______________________________________________ asdf-devel mailing list asdf-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On 18 Apr 2012, at 15:39, Robert Goldman wrote:
On 4/18/12 Apr 18 -12:10 AM, Pascal Costanza wrote:
On 17 Apr 2012, at 21:36, Robert Goldman <rpgoldman@sift.info> wrote:
I am willing to run the ASDF tests using RMCL, since my Mac still has Snow Leopard, instead of Lion.
*However*, as a non-RMCL user, I have no idea how to run it from the shell, so that we can run the test suite on RMCL.
Can someone please offer me a clue?
You can't run RMCL from a shell...
Hm. Well then I cannot run the tests there. Maybe someone who is dedicated to seeing RMCL + ASDF continue to work would be so kind as to provide a technique for running the tests. This may be quite tricky, since the tests require restarting lisp in pristine state.
Question: is it possible to control RMCL using applescript? I suppose that could be used to perform the functions for which we are currently using shell scripts. An ongoing rewrite effort to get the tests to work is likely to be quite laborious.
Given that we cannot test on RMCL, and it's EOLed by the release of Lion, I am inclined to say we should end official ASDF support for RMCL. Incorporating patches to keep ASDF working on RMCL seems fine, but I don't believe that we can continue to fix problems on that platform ourselves.
I can't be trying to run this from the GUI every time it needs a test. I had to give up testing LispWorks for the same reason.
...but you can run LispWorks from a shell.
Actually, you can run LispWorks from a shell, but only if you can dump an image, which is a privilege limited to those who have a full (paid) license.
I don't have such a license, so I cannot run the LispWorks tests.
It would be nice if someone from the community (someone working for LispWorks, perhaps) would take the responsibility of verifying that ASDF releases run on LW. I don't believe Faré can do this, either.
Why is it that ASDF requires restarting lisp in a pristine state? For my projects, I always have both shell scripts and "pure" lisp versions. That also helps with testing in the LispWorks IDE... Pascal -- Pascal Costanza
On Sun, Apr 22, 2012 at 08:54, Pascal Costanza <pc@p-cos.net> wrote:
Why is it that ASDF requires restarting lisp in a pristine state?
Mostly historical reasons. Its test suite predates most test-suite software. No one has rewritten it to use anything else. I would gladly accept a patch that replaces that with, say, fiveam or stefil. Proper use of clear-system and delete-package can help. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Bragg's principle: Everything in the future is a wave, everything in the past is a particle.
On 4/22/12 Apr 22 -9:55 AM, Faré wrote:
On Sun, Apr 22, 2012 at 08:54, Pascal Costanza <pc@p-cos.net> wrote:
Why is it that ASDF requires restarting lisp in a pristine state?
Mostly historical reasons. Its test suite predates most test-suite software. No one has rewritten it to use anything else. I would gladly accept a patch that replaces that with, say, fiveam or stefil. Proper use of clear-system and delete-package can help.
I suppose it could be rewritten to do that. I have never thought it was worth the trouble, since running the tests would damage the state of any lisp process in which it was run (because of changing the internal state of ASDF), but such a rewrite would make ASDF testable on LW personal and RMCL, which would be a worthwhile objective. Sadly, FiveAM seems to have been abandoned and is in need of a new maintainer. None of the bese projects darcs repos has been modified in almost 2 years.... My work has become very busy of late, so I don't have time to do such a rewrite, but I believe it is well within reach. Best, r
On Sun, 2012-04-22 at 10:18 -0500, Robert Goldman wrote:
On 4/22/12 Apr 22 -9:55 AM, Faré wrote:
On Sun, Apr 22, 2012 at 08:54, Pascal Costanza <pc@p-cos.net> wrote:
Why is it that ASDF requires restarting lisp in a pristine state?
Mostly historical reasons. Its test suite predates most test-suite software. No one has rewritten it to use anything else. I would gladly accept a patch that replaces that with, say, fiveam or stefil. Proper use of clear-system and delete-package can help.
I suppose it could be rewritten to do that. I have never thought it was worth the trouble, since running the tests would damage the state of any lisp process in which it was run (because of changing the internal state of ASDF), but such a rewrite would make ASDF testable on LW personal and RMCL, which would be a worthwhile objective.
Sadly, FiveAM seems to have been abandoned and is in need of a new maintainer. None of the bese projects darcs repos has been modified in almost 2 years....
Somebody complained about that on bordeaux-threads-devel, so I picked it up: http://fenlix.dreamwidth.org/2255.html -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib
On 4/22/12 Apr 22 -10:21 AM, Stelian Ionescu wrote:
On Sun, 2012-04-22 at 10:18 -0500, Robert Goldman wrote:
On 4/22/12 Apr 22 -9:55 AM, Faré wrote:
On Sun, Apr 22, 2012 at 08:54, Pascal Costanza <pc@p-cos.net> wrote:
Why is it that ASDF requires restarting lisp in a pristine state?
Mostly historical reasons. Its test suite predates most test-suite software. No one has rewritten it to use anything else. I would gladly accept a patch that replaces that with, say, fiveam or stefil. Proper use of clear-system and delete-package can help.
I suppose it could be rewritten to do that. I have never thought it was worth the trouble, since running the tests would damage the state of any lisp process in which it was run (because of changing the internal state of ASDF), but such a rewrite would make ASDF testable on LW personal and RMCL, which would be a worthwhile objective.
Sadly, FiveAM seems to have been abandoned and is in need of a new maintainer. None of the bese projects darcs repos has been modified in almost 2 years....
Somebody complained about that on bordeaux-threads-devel, so I picked it up: http://fenlix.dreamwidth.org/2255.html
That's great. Any chance of you taking over the fiveam page on common-lisp.net and fixing it so it's no longer misleading? Right now it's a decoy pointer to bad stuff. If Marco has given you ownership, taking over the common-lisp.net page for bese.it would be a kindness, if only to point out the transfer. [let's take this off-list now, if there's anything more.] Best, r
On Sun, 2012-04-22 at 11:01 -0500, Robert Goldman wrote:
Sadly, FiveAM seems to have been abandoned and is in need of a new maintainer. None of the bese projects darcs repos has been modified in almost 2 years....
Somebody complained about that on bordeaux-threads-devel, so I picked it up: http://fenlix.dreamwidth.org/2255.html
That's great. Any chance of you taking over the fiveam page on common-lisp.net and fixing it so it's no longer misleading? Right now it's a decoy pointer to bad stuff.
You mean http://common-lisp.net/project/bese/FiveAM.html ? I'll change it to point to http://common-lisp.net/project/fiveam/ -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib
participants (4)
-
Faré -
Pascal Costanza -
Robert Goldman -
Stelian Ionescu