Few standard packages have sage-check to check them.
Dr. David Kirkby
which have a file 'spkg-check' which will execute a test routine after building
in the event the environment variable SAGE_CHECK is set to yes.
The number is depressingly small, at only 19.
./atlas-3.8.3.p12/spkg-check
./cddlib-094f.p6/spkg-check
./eclib-20080310.p10/spkg-check
./ecm-6.2.1.p2/spkg-check
./f2c-20070816.p2/spkg-check
./flint-1.5.0.p4/spkg-check
./givaro-3.2.13rc2.p1/spkg-check
./gsl-1.10.p2/spkg-check
./iconv-1.13.1.p2/spkg-check (Of course, since I added iconv!)
./libfplll-3.0.12.p0/spkg-check
./libgcrypt-1.4.4.p3/spkg-check
./mpfr-2.4.2/spkg-check
./mpir-1.2.2.p1/spkg-check
./ntl-5.4.2.p12/spkg-check
./r-2.10.1.p1/spkg-check
./sagetex-2.2.5/spkg-check
./scipy-0.7.p5/spkg-check
./sqlalchemy-0.5.8/spkg-check
./zn_poly-0.9.p4/spkg-check
That leaves all these which do not run any self-tests, several of which have
self-test routines, but which never get executed in Sage, even if SAGE_CHECK =
yes, since nobody has written a sage-check.
Should spkg-check be added to these to enable self-tests when "SAGE_CHECK=yes"?
./blas-20070724/spkg-install // there are NO tests in blas
./boehm_gc-7.1.p5/spkg-install // HAS self tests, but no spkg-check
./boost-cropped-1.34.1/spkg-install // there are NO self tests
./cephes-2.8/spkg-install // HAS self tests, but no spkg-check
./cliquer-1.2.p5/spkg-install
./conway_polynomials-0.2/spkg-install
./cvxopt-0.9.p8/spkg-install
./cython-0.12.1/spkg-install
./docutils-0.5.p0/spkg-install
./ecl-10.2.1/spkg-install
./elliptic_curves-0.1/cremona_mini/spkg-install
./elliptic_curves-0.1/ellcurves/spkg-install
./elliptic_curves-0.1/spkg-install
./examples-4.4.4.alpha1/spkg-install
./extcode-4.4.4.alpha1/spkg-install
./flintqs-20070817.p4/spkg-install
./fortran-20100428/spkg-install
./freetype-2.3.5.p2/spkg-install
./gap-4.4.12.p3/spkg-install
./gd-2.0.35.p5/spkg-install
./gdmodule-0.56.p7/spkg-install
./genus2reduction-0.3.p6/spkg-install
./gfan-0.4plus.p1/spkg-install
./ghmm-20080813.p0/spkg-install
./gnutls-2.2.1.p5/spkg-install
./graphs-20070722.p1/spkg-install
./iml-1.0.1.p12/spkg-install
./ipython-0.9.1.p0/spkg-install
./jinja-1.2.p0/spkg-install
./jinja2-2.1.1.p0/spkg-install
./lapack-20071123.p1/spkg-install
./lcalc-20100428-1.23/spkg-install
./libgpg_error-1.6.p3/spkg-install
./libm4ri-20100221/spkg-install
./libpng-1.2.35.p2/spkg-install
./linbox-1.1.6.p3/spkg-install
./matplotlib-0.99.1.p4/spkg-install
./maxima-5.20.1.p0/spkg-install
./mercurial-1.3.1.p2/spkg-install
./moin-1.9.1.p1/spkg-install
./mpfi-1.3.4-cvs20071125.p8/spkg-install
./mpmath-0.14/spkg-install
./networkx-1.0.1/spkg-install
./numpy-1.3.0.p3/spkg-install
./opencdk-0.6.6.p4/spkg-install
./palp-1.1.p2/spkg-install
./pari-2.3.5.p1/spkg-install
./pexpect-2.0.p4/spkg-install
./pil-1.1.6.p2/spkg-install
./polybori-0.6.4.p1/spkg-install
./polytopes_db-20100210/spkg-install
./pycrypto-2.0.1.p5/spkg-install
./pygments-0.11.1.p0/spkg-install
./pynac-0.2.0.p3/spkg-install
./python_gnutls-1.1.4.p7/spkg-install
./python-2.6.4.p8/spkg-install
./ratpoints-2.1.3.p1/spkg-install
./readline-6.0.p1/spkg-install
./rubiks-20070912.p10/spkg-install
./sage_scripts-4.4.4.alpha1/spkg-install
./sage-4.4.4.alpha1/spkg-install
./sagenb-0.8.p2/spkg-install
./scipy_sandbox-20071020.p5/spkg-install
./scons-1.2.0/spkg-install
./setuptools-0.6c9.p0/spkg-install
./singular-3-1-0-4-20100214/spkg-install
./singular-3.1.0.4.p6/spkg-install
./sphinx-0.6.3.p4/spkg-install
./sqlite-3.6.22/spkg-install
./symmetrica-2.0.p5/spkg-install
./sympow-1.018.1.p7/spkg-install
./sympy-0.6.4.p0/spkg-install
./tachyon-0.98beta.p11/spkg-install
./termcap-1.3.1.p1/spkg-install
./twisted-9.0.p2/spkg-install
./weave-0.4.9.p0/spkg-install
./zlib-1.2.3.p5/spkg-install
./zodb3-3.7.0.p3/spkg-install
William Stein
> I've just done a quick check to see the number of standard packages in Sage which have a file 'spkg-check' which will execute a test routine after building in the event the environment variable SAGE_CHECK is set to yes.
>
> The number is depressingly small, at only 19.
>
> ./atlas-3.8.3.p12/spkg-check
> ./cddlib-094f.p6/spkg-check
> ./eclib-20080310.p10/spkg-check
> ./ecm-6.2.1.p2/spkg-check
> ./f2c-20070816.p2/spkg-check
> ./flint-1.5.0.p4/spkg-check
> ./givaro-3.2.13rc2.p1/spkg-check
> ./gsl-1.10.p2/spkg-check
> ./iconv-1.13.1.p2/spkg-check (Of course, since I added iconv!)
> ./libfplll-3.0.12.p0/spkg-check
> ./libgcrypt-1.4.4.p3/spkg-check
> ./mpfr-2.4.2/spkg-check
> ./mpir-1.2.2.p1/spkg-check
> ./ntl-5.4.2.p12/spkg-check
> ./r-2.10.1.p1/spkg-check
> ./sagetex-2.2.5/spkg-check
> ./scipy-0.7.p5/spkg-check
> ./sqlalchemy-0.5.8/spkg-check
> ./zn_poly-0.9.p4/spkg-check
>
> That leaves all these which do not run any self-tests, several of which have self-test routines, but which never get executed in Sage, even if SAGE_CHECK = yes, since nobody has written a sage-check.
>
> Should spkg-check be added to these to enable self-tests when "SAGE_CHECK=yes"?
>
Emphatic yes!
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
Dr. David Kirkby
I'll do a few until I get bored!
I just noticed that despite the fact flint has a test suite, and an spkg-check
file, the spkg-check suffers from the usual
if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then
echo "64 bit MacIntel"
FLINT_TUNE=" -fPIC -m64 -funroll-loops"
fi
so any attempt to test flint in 64-bit mode on OpenSolaris fails miserably. As
soon as I removed the restriction of building 64-bit on OS X, so all the tests
passed.
That is now
http://trac.sagemath.org/sage_trac/ticket/9277
So those ****ing SAGE64's still haunt me! I thought removing them from
spkg-install would be enough, but no, there are more of them! Luckily, with only
19 spkg-check files, there can't be too many SAGE64 issues and I would expect
many will not need any changing.
Dave
Dr. David Kirkby
>> I've just done a quick check to see the number of standard packages in Sage which have a file 'spkg-check' which will execute a test routine after building in the event the environment variable SAGE_CHECK is set to yes.
>>
>> The number is depressingly small, at only 19.
>> <SNIP a big list>
>> which do not run any self-tests, several of which have self-test routines, but which never get executed in Sage, even if SAGE_CHECK = yes, since nobody has written a sage-check.
>>
>> Should spkg-check be added to these to enable self-tests when "SAGE_CHECK=yes"?
>>
>
>
> Emphatic yes!
I created a metaticket at
http://trac.sagemath.org/sage_trac/ticket/9281
to show what packages have spkg-install files.
It will also have the result of the tests when SAGE_CHECK is "yes" on
OpenSolaris x64.
* Some of the packages do not need spkg-check files, such as those elliptic
curve ones that just copy files and spkg-install confirms the files are copied ok.
* Some of the upstream packages have no test suites.
* Many upstream packages do have test suites, but Sage does not execute the
tests. These need fixing.
* Flint, and possibly some other packages have test suites that build 32-bit
when a 64-bit build is attempted on OpenSolaris. That was very easy to fix
(#9277, awaiting review)
* ECL I believe has a test suite, but one needs to download a datafile to
perform the tests. That may or may not be too big to consider adding to Sage.
Hopefully, with time, the spkg-check files will get added.
It would be REALLY useful if people add spkg-check files when they make changes
to standard packages. Anyone who tried to do the lot would die of boredom, but
if everyone done it when they was changing a package, it would not be such a chore.
Dave