On Tue, Dec 6, 2011 at 11:03 AM, Dima Pasechnik <dimpase+...@gmail.com>wrote:
> Sage has a buildbot. So the question is to put the tests you need in the
> Sage's ECL spkg, and extract the results of the
> buildbot. This will give you results of tests of ECL released with Sage,
> on the corresponding list of platforms.
>
That would only test ECL in Sage, not ECL in all the platforms with the
particular tests we use (quicklisp, for instance, etc), am I wrong?
> By the way, could you point us the changes you made to ECL to prevent it
> from suffering the constant fork() failures?
>
I am afraid I did not explain myself very well in the last emails: ECL does
not fix fork() it simply avoids using it in cygwin. This means we have to
use system(), which is only useful in some contexts and may even cause some
problems with argument parsing.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
