On Sun, Dec 28, 2008 at 6:08 AM, Pablo De Napoli pden...@gmail.com wrote:
Another possibility would be to have a list of the packages to be tested in
SKPG_CHECK like
SPKG_CHECK=ntl flint
(Under bash substrings can be checking wihth something line
if [[ $SAGE_CHECK == *flint* ]]
then
On Dec 28, 2:51 pm, William Stein wst...@gmail.com wrote:
On Sun, Dec 28, 2008 at 6:08 AM, Pablo De Napoli pden...@gmail.com wrote:
Another possibility would be to have a list of the packages to be tested in
SKPG_CHECK like
SPKG_CHECK=ntl flint
(Under bash substrings can be
On Sun, Dec 28, 2008 at 3:20 PM, mabshoff mabsh...@googlemail.com wrote:
On Dec 28, 2:51 pm, William Stein wst...@gmail.com wrote:
On Sun, Dec 28, 2008 at 6:08 AM, Pablo De Napoli pden...@gmail.com wrote:
Another possibility would be to have a list of the packages to be tested in
I see that the file skpg-install for flint needs to be modified in final
releases to avoid runing the test suite.
I think it would be better to have for example an environment variable like
SAGE_RUN_FLINT_TESTSUITE (and run the test suite or not depending on the value
of that variable) that
On Dec 27, 8:31 am, Pablo De Napoli pden...@gmail.com wrote:
Hi Pablo,
I see that the file skpg-install for flint needs to be modified in final
releases to avoid runing the test suite.
There was already a ticket to do that before 3.2.3.a0 was even
released :)
I think it would be better
SAGE_CHECK=yes does that for every spkg, adding 50+ env variables for
all the spkgs seems like a bad idea and won't automatically force the
test suite when we want it to be tested.
I agree. 50+ env-variables is not a good idea.
SAGE_CHECK is ok
Cheers,
Pablo
On an intel macbook running OS 10.4, the build seems to be stuck on
All tests passed
FLINT_BITS = 32
snip
Testing fmpz_poly_CRT_unsigned()... ok
Testing fmpz_poly_CRT()... ok
Testing fmpz_poly_gcd_subresultant()... ok
Testing fmpz_poly_gcd_modular()...
On Wed, Dec 24, 2008 at 6:09 PM,
On Fri, Dec 26, 2008 at 12:57 PM, mabshoff mabsh...@googlemail.com wrote:
On Dec 26, 9:54 am, David Joyner wdjoy...@gmail.com wrote:
Hi David,
On an intel macbook running OS 10.4, the build seems to be stuck on
All tests passed
FLINT_BITS = 32
snip
Testing
On Dec 26, 10:02 am, David Joyner wdjoy...@gmail.com wrote:
Hi David,
FLINT_BITS = 32
SNIP
This issue has already been reported and is fixed at #4879 which will
be in 3.2.3.rc0.
Please read the release thread before reporting issues.
Sorry, I read it but obviously didn't
Ok, we are having a problem with the new FLINT on 32 bit boxen, i.e.
32 bit Linux:
Testing fmpz_poly_CRT()... ok
Testing fmpz_poly_gcd_subresultant()... ok
Testing fmpz_poly_gcd_modular()... FAIL!
Testing fmpz_poly_resultant()... ok
Testing fmpz_poly_2norm()... ok
Testing
On Dec 25, 4:30 am, mabshoff mabsh...@googlemail.com wrote:
Ok, we are having a problem with the new FLINT on 32 bit boxen, i.e.
32 bit Linux:
Testing fmpz_poly_CRT()... ok
Testing fmpz_poly_gcd_subresultant()... ok
Testing fmpz_poly_gcd_modular()... FAIL!
Testing
On Thu, Dec 25, 2008 at 10:53 AM, mabshoff mabsh...@googlemail.com wrote:
On Dec 25, 4:30 am, mabshoff mabsh...@googlemail.com wrote:
Ok, we are having a problem with the new FLINT on 32 bit boxen, i.e.
32 bit Linux:
Testing fmpz_poly_CRT()... ok
Testing fmpz_poly_gcd_subresultant()...
On Dec 25, 11:02 am, William Stein wst...@gmail.com wrote:
On Thu, Dec 25, 2008 at 10:53 AM, mabshoff mabsh...@googlemail.com wrote:
SNIP
And Bill Hart has fixed the bug in FLINT 1.0.21, so I am waiting on
some more tests to finish and some build reports before cutting
3.2.3.final.
On amd64 ubuntu 8.10, build went fine but sage -testall had
--
The following tests failed:
sage -t devel/sage/sage/calculus/calculus.py
sage -t devel/sage/sage/modules/free_module_element.pyx
sage -t
14 matches
Mail list logo
