LispWorks for Windows 32 bits

[tusc...@gmail.com]

Hello,

I can offer testing for LispWorks 6.1.1 32 bits Professional on Windows XP-SP3 or Windows 8.1.
I also have LispWorks 64 bits on Mac OS X, and my computer is a MacBook Pro late 2013 running Mavericks 10.9.1.
And hey, I have a Raspberry Pi running CCL, poor thing not sure if it can handle the load.

Please let me know if that can be of some interest for your project.

Best,
Camille

[Anton Vodonosov]

Hi Camille,

Thanks a lot for your proposal.

As for LispWorks on Mac - last month Dave Cooper contributed results,
I hope he will be able to run tests in the future too.

But Windows LispWorks is not covered, it would be very welcome if you help here.

Raspbery Pi is also very interesting. Testing is not so heavy load,
basically all the work is done sequentially. But it may take 2-3 GB of
disk space to download and build all the Quicklisp libraries.
If the system has Internet connection and this disk space, lets
try to run tests there.

Let me know what help is needed.

05.01.2014, 15:33, "tusc...@gmail.com" <tusc...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups "cl-test-grid" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cl-test-grid...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Camille Troillard]

Hello Anton,

On Monday, January 6, 2014 1:45:15 PM UTC+1, Anton Vodonosov wrote:

Thanks a lot for your proposal.

As for LispWorks on Mac - last month Dave Cooper contributed results,
I hope he will be able to run tests in the future too.

But Windows LispWorks is not covered, it would be very welcome if you help here.

OK.
 

Raspbery Pi is also very interesting. Testing is not so heavy load,
basically all the work is done sequentially. But it may take 2-3 GB of
disk space to download and build all the Quicklisp libraries.
If the system has Internet connection and this disk space, lets
try to run tests there.

A fun project in perspective!
 

Let me know what help is needed.

I'll let you know how it goes, thanks for your help.


Cam

 

[Anton Vodonosov]

Hi Camille, 

 

CCL results from your Raspbery Pi have just arrived.

 

Thanks a lot!

 

Looks like the testing took 22.3 hours.

 

Here is the comparison of the Raspbery Pi results and x86 linux results:

http://common-lisp.net/project/cl-test-grid/ccl/ccl-raspbery-pi-diff.html

 

It is impressive, CCL on Raspbery Pi works almost the same as on x86.

 

Some improvements (i.e. green results on arm comparing to red results on x86)

are caused by newer ASDF on your CCL (moptilities, metatilities, tinaa, and

many other failures caused by "Component :CLOSER-MOP does not match version 0.55"

error). Also your Raspbery Pi system seems to have SDL libraries installed, which

allows to libpbuilder-sdl and systems depending on it to load OK.

 

And the Raspbery Pi system has just several regressions.

 

Here is the full table of test results for Raspbery Pi CCL:

http://common-lisp.net/project/cl-test-grid/ccl/ccl-raspbery-pi.html

 

Best regards,

- Anton

[Camille Troillard]

That's great! Yeah, I am impressed too. Not only by the fine job that folks at CCL have done but also by the device and the distribution. The Raspbian GNU Linux system was practically untouched, I only had to install git I believe.

The test suite ran without any problem (it was the first time I ran it), and was rather easy to configure.

Would you like me to setup a cron job to run tests every months?
I was thinking it would be nice to test the new alpha quicklisp distribution as well.

Now I am going to run the tests on Windows, but first I have to solve problems with LispWorks and pathnames from the command line.

Best,
Cam

[Camille Troillard]

Hello Anton,

Please have a look at the following email with an answer from Martin Simmons at the end.

Do you think the lisp-exe system can be changed accordingly to what Martin recommends?

Cam

-----

On Tue, 7 Jan 2014 19:32:06 +0100, Camille Troillard said:

Hello,

I am trying to launch a LispWorks 6.1 process from Clozure CL.

It is invoked from CCL like this (this is the exact command constructed in CCL):

C:\Progra~1\LispWorks\lispworks-6-1-0-x86-win32 -init - -siteinit - -eval (load #P"C:/lisp/cl-test-grid/agent/proc-common.lisp") -eval (set-response #P"C:/lisp/cl-test-grid/work-dir/agent/response2714567116176465343.lisp" "abcs *() { /d e11 ") -eval (lispworks:quit)

LispWorks is launched but falls into the debugger with the following error:

Reader cannot find package C.

The string argument to READ-FROM-STRING being:

"(load #P\\C:/lisp/cl-test-grid/agent/proc-common.lisp\\)"

It seems something wrong happened to the quotes around the pathname.

Do you know how can I work around this problem?

Sorry, the command line parser doesn't do the correct thing with quotes and
backslashes on Windows, so the recommended workaround is to put all of the
forms in a file and use the -build or -load options to load it.

-- 
Martin Simmons

[Camille Troillard]

I have implemented a solution that worked, though 100% satisfying at the moment.

If this is alright for you, I suggest with discuss about this off-line.

Cam

--
You received this message because you are subscribed to a topic in the Google Groups "cl-test-grid" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cl-test-grid/VH4oHb47riU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cl-test-grid...@googlegroups.com.

[Anton Vodonosov]

08.01.2014, 12:51, "Camille Troillard" <tusc...@gmail.com>:

> Would you like me to setup a cron job to run tests every months?

That would be great.

Could you run it more often? It automatically checks if new
quicklisp is available, and if nothing new then it just exits.
It can be run daily.

> I was thinking it would be nice to test the new alpha quicklisp distribution as well.

Lets postpone that. cl-test-grid will do that automatically.
It isn't implemented yet; I have run qlalpha tests by patching cl-test-grid on my machine,
but anyway, lets fix LispWorks problems first.

Best regards,
- Anton

[Anton Vodonosov]

Hi, thanks for the info.

Yes, pass the code to execute via temporary file, I hope to implement it soon.
I will override lisp-exe::start-lisp-process for lisp-exe:lisp-works.


09.01.2014, 02:27, "Camille Troillard" <cam...@osculator.net>:

> You received this message because you are subscribed to the Google Groups "cl-test-grid" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to cl-test-grid...@googlegroups.com.

[Anton Vodonosov]

Hi Camille,

I have finally incorporated the fix for LispWorks on Windows.
The final fix differs somewhat from your draft -
I store temporary script in the current test-run directry
(as it is already done for temporary response files
used to return result from child lisp process to the parent).

I also started some refactoring, in particular removed
the deprecated function lisp-exe:run-lisp-process.

Could you test the current cl-test-grid version to run
lisp-works? Possible test code:

(ql:quickload :test-grid-agent)
(defparameter *lispworks*
(make-instance 'lisp-exe:lispworks
:exe-path "C:\\Path\\To\\LispWorks.exe"))

(tg-agent::implementation-identifier *lispworks*)

BTW, does (win32:dismiss-splash-screen t) fix the splash
screen problem?

Also, LispWorks docs mention (load-all-patches) function:
http://www.lispworks.com/documentation/lw50/LWUG/html/lwuser-372.htm
Do you think we should include this call?

PS

Thanks for your LispWorks results - they are published already.
When reviewing the results I even found and submitted a bug in LispWorks:
https://bugs.launchpad.net/common-lisp/+bug/1268779

Best regards,
- Anton

[Camille Troillard]

Hello Anton,

On 17 Jan 2014, at 02:11, Anton Vodonosov <avodo...@yandex.ru> wrote:

> I have finally incorporated the fix for LispWorks on Windows.
> The final fix differs somewhat from your draft -
> I store temporary script in the current test-run directry
> (as it is already done for temporary response files
> used to return result from child lisp process to the parent).
>
> I also started some refactoring, in particular removed
> the deprecated function lisp-exe:run-lisp-process.

Nice!

> Could you test the current cl-test-grid version to run
> lisp-works? Possible test code:
>
> (ql:quickload :test-grid-agent)
> (defparameter *lispworks*
> (make-instance 'lisp-exe:lispworks
> :exe-path "C:\\Path\\To\\LispWorks.exe"))
>
> (tg-agent::implementation-identifier *lispworks*)

I pulled latest changes from cl-test-grid and added the directory to quicklisp’s list of local projects.

The test using CCL as host Lisp was successful. There is a small trick regarding the exe-path though (see attached test-agent-ccl-20140120.txt), that I already had to use in my current run-agent.lisp, so I can run the tests; I somewhat forgot to tell you about that.

Out of curiosity, I also tested this code with LispWorks Windows 32 bits to see if I can use it as a test agent, but it fails. It seems the external-program library is not calling the correct function under Windows. I guess this can wait for the moment.

[Anton Vodonosov]

20.01.2014, 14:24, "Camille Troillard" <tusc...@me.com>:

> I pulled latest changes from cl-test-grid and added the directory to quicklisp’s list of local projects.

Probably you know this, an alternative to configuring quicklisp/local-projects/ is to

(pushnew "C:/path/to/cl-test-grid/" asdf:*central-registry* :test #'equal)

and ql:quickload will work for cl-test-grid modules. I usually do it that way.

> The test using CCL as host Lisp was successful.  There is a small trick regarding the exe-path though (see attached test-agent-ccl-20140120.txt), that I already had to use  in my current run-agent.lisp, so I can run the tests; I somewhat forgot to tell you about that.
>

This is very puzzling. Paths in the form "C:\\Program Files\\...\" work for me
when agent is run by CCL 1.8 and CCL 1.9.

What CCL version do you use?

> Out of curiosity, I also tested this code with LispWorks Windows 32 bits to see if I can use it as a test agent, but it fails.  It seems the external-program library is not calling the correct function under Windows.  I guess this can wait for the moment.

Yes, external-program is the main portability limitation for test-grid-agent.
Currently I recommend to use CCL for it. Today there is uiop:run-program
which is more portable. I hope someday in the future to migrate to it.
But it will require not only code changes, but testing with various child lisps
on various OSes, so I postpone this task; there are more demanding tasks
to solve.

>
> ,>  BTW, does (win32:dismiss-splash-screen t) fix the splash
>>  screen problem?
>
> No, unlike what is explained in LW’s Knowledge base (see http://www.lispworks.com/kb/480e08fa45a7a09b80256be400486160.html), the call to (win32:dismiss-splash-screen t) in the init file does not dismiss the splash screen.
>
> The only reliable way to do that seem to create a console only executable.  I tried that but ran into other problems, again I will spend some more time when there is a Quicklisp distribution update.

If this splash screen bothers you, you can experiment with -build or -siteinit options.
IMHO, if the splash screen does not require user to click buttons or take other actions,
it's not a big inconvenience, if any.

[Anton Vodonosov]

>>  Also, LispWorks docs mention (load-all-patches) function:
>>  http://www.lispworks.com/documentation/lw50/LWUG/html/lwuser-372.htm
>>  Do you think we should include this call?
>

> This is correct, and I forgot to add it to the test-grid agent generated initialisation files.

Added (load-all-patches) to lisp-exe.

>
>>  PS
>>
>>  Thanks for your LispWorks results - they are published already.
>>  When reviewing the results I even found and submitted a bug in LispWorks:
>>  https://bugs.launchpad.net/common-lisp/+bug/1268779
>

> That’s great.
> Regarding the LispWorks results, is there a URL where I can visit them?
> I search the documentation but can only find programmatic access to the results.


No, There is no such URL. If you are interested, I generated two example reports:
LispWorks on Windows compared to SBCL on Linux:
http://common-lisp.net/project/cl-test-grid/lispworks/lw-sbcl-diff.html

All LispWorks Windows results:
http://common-lisp.net/project/cl-test-grid/lispworks/lw-results.html

They are generated using the attached sample script.
Working with such script from slime is my user interface for cl-test-grid.

Best regards,
- Anton

[Anton Vodonosov]

22.01.2014, 03:23, "Anton Vodonosov" <avodo...@yandex.ru>:

> 20.01.2014, 14:24, "Camille Troillard" <tusc...@me.com>:

>>  Regarding the LispWorks results, is there a URL where I can visit them?
>>  I search the documentation but can only find programmatic access to the results.
>
> No, There is no such URL.

Let me put it other way: the URL is cl-tes...@googlegroups.com - submit plain English request here
and it will respond with the report URL, if possible.

Best regards,
- Anton

[Camille Troillard]

On 22 Jan 2014, at 05:55, Anton Vodonosov <avodo...@yandex.ru> wrote:

>>> Regarding the LispWorks results, is there a URL where I can visit them?
>>> I search the documentation but can only find programmatic access to the results.
>>
>> No, There is no such URL.
>
> Let me put it other way: the URL is cl-tes...@googlegroups.com - submit plain English request here
> and it will respond with the report URL, if possible.

AI based test reports, fantastic!