[sage-devel] Re: Bad CEq in Find_Equations
Fixed it. It was a bad build of PALP built with -DNDEBUG.
Isuru
On Wed, Jan 1, 2020 at 5:34 AM Isuru Fernando wrote:
> I get thousands of test failures in 9.0.rc1 due to an error from palp. Any
> ideas?
>
> Isuru
>
> sage: toric_varieties.dP6()
> Bad CEq in Find_Equations
> ---
> ValueErrorTraceback (most recent call last)
> in ()
> > 1 toric_varieties.dP6()
>
> /projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/schemes/toric/library.pyc
> in dP6(self, names, base_ring)
> 313 (x, u, y, v, z, w)
> 314 """
> --> 315 return self._make_CPRFanoToricVariety('dP6', names,
> base_ring)
> 316
> 317 def dP7(self, names='x u y v z', base_ring=QQ):
>
> /projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/schemes/toric/library.pyc
> in _make_CPRFanoToricVariety(self, name, coordinate_names, base_ring)
> 265 if dict_key not in self.__dict__:
> 266 polytope = LatticePolytope(rays,
> lattice=ToricLattice(len(rays[0])))
> --> 267 points = [tuple(_) for _ in polytope.points()]
> 268 ray2point = [points.index(r) for r in rays]
> 269 charts = [ [ray2point[i] for i in c] for c in cones ]
>
> /projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/geometry/lattice_polytope.pyc
> in points(self, *args, **kwds)
>3746 if self.dim() == self.lattice_dim():
>3747 print(type(result), result)
> -> 3748 points =
> read_palp_point_collection(StringIO(result), M)
>3749 else:
>3750 m = self._embed(read_palp_matrix(result))
>
> /projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/geometry/point_collection.pyx
> in sage.geometry.point_collection.read_palp_point_collection
> (build/cythonized/sage/geometry/point_collection.c:8111)()
> 998 return None
> 999 first_line = first_line.split()
> -> 1000 m = int(first_line[0])
>1001 n = int(first_line[1])
>1002 if m >= n:
>
> ValueError: invalid literal for int() with base 10: 'Bad'
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CA%2B01voPCpnrnuYcBRtmDLweGDzLpJ%2BNyR%2BNwqhBJYGfAN%3Dq6wA%40mail.gmail.com.
[sage-devel] Bad CEq in Find_Equations
I get thousands of test failures in 9.0.rc1 due to an error from palp. Any
ideas?
Isuru
sage: toric_varieties.dP6()
Bad CEq in Find_Equations
---
ValueErrorTraceback (most recent call last)
in ()
> 1 toric_varieties.dP6()
/projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/schemes/toric/library.pyc
in dP6(self, names, base_ring)
313 (x, u, y, v, z, w)
314 """
--> 315 return self._make_CPRFanoToricVariety('dP6', names,
base_ring)
316
317 def dP7(self, names='x u y v z', base_ring=QQ):
/projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/schemes/toric/library.pyc
in _make_CPRFanoToricVariety(self, name, coordinate_names, base_ring)
265 if dict_key not in self.__dict__:
266 polytope = LatticePolytope(rays,
lattice=ToricLattice(len(rays[0])))
--> 267 points = [tuple(_) for _ in polytope.points()]
268 ray2point = [points.index(r) for r in rays]
269 charts = [ [ray2point[i] for i in c] for c in cones ]
/projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/geometry/lattice_polytope.pyc
in points(self, *args, **kwds)
3746 if self.dim() == self.lattice_dim():
3747 print(type(result), result)
-> 3748 points =
read_palp_point_collection(StringIO(result), M)
3749 else:
3750 m = self._embed(read_palp_matrix(result))
/projects/66d93023-00f0-4c12-8a25-5d6d4e486740/miniconda3/envs/sage90/lib/python2.7/site-packages/sage/geometry/point_collection.pyx
in sage.geometry.point_collection.read_palp_point_collection
(build/cythonized/sage/geometry/point_collection.c:8111)()
998 return None
999 first_line = first_line.split()
-> 1000 m = int(first_line[0])
1001 n = int(first_line[1])
1002 if m >= n:
ValueError: invalid literal for int() with base 10: 'Bad'
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CA%2B01voMgtPemo49JMcpxMtHKmU68JOBLMLXELPD83E9FSeLWAQ%40mail.gmail.com.
Re: [sage-devel] Re: Buiding sage on a Raspberry Pi 4B
I wanted to say "...have NO spool ..." Apologize. t.d. Le 31/12/2019 à 19:10, Thierry Dumont a écrit : > > Are you sure you don't have a problem with the size of the ram ? You > certainly have spool virtual memory partition. > > I have run some programs on a PI (3) (not Sage), and when the memory > was full, I have got some segmentation faults (this should not happen, > but..). This was on raspbian, two years ago. > > Yours, > > t.d. > > Le 31/12/2019 à 11:36, Jaap Spies a écrit : >> I did run the failing tests! This is really frustrating. >> >> >> ./sage -t --long src/sage/rings/tests.py # Killed due to >> segmentation fault NOW: All test passed!! >> ./sage -t --long >> src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed due >> to segmentation fault NOW: All test passed!! >> ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to >> segmentation fault NOW: All test passed!! >> ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure >> len(LE) Expected 1 Got: 50 >> ./sage -t --long >> src/sage/modular/modform_hecketriangle/abstract_space.py # Killed due >> to segmentation fault NOW: All test passed!! >> ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # >> Timed out NOW: All test passed!! in NB 51.16 seconds >> ./sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # >> Timed out total time 1832.3 seconds NOW: All test passed in 11.74 seconds >> ./sage -t --long >> src/sage/combinat/designs/evenly_distributed_sets.pyx # Timed out >> NOW: All test passed in 8.11 seconds >> ./sage -t --long src/sage/modular/modform/tests.py # Times out >> 1822.7 seconds NOW: All test passed in 4.12 seconds >> ./sage -t --long src/sage/sets/set.py # Times out 1821.5 seconds >> NOW: All test passed in 2.08 seconds >> ./sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed >> ./sage -t --long src/sage/cpython/dict_del_by_value.pyx # 1 doctest >> failed >> >> >> On Tuesday, December 31, 2019 at 10:58:38 AM UTC+1, Jaap Spies wrote: >> >> >> >> On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote: >> >> >> >> I'll make a bash script to do the tests stand alone. >> >> >> >> bash test_errors_rc1 >> err.log 2>&1 & >> >> Resume: >> ./sage -t --long src/sage/rings/tests.py # Killed due to >> segmentation fault >> ./sage -t --long >> src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed >> due to segmentation fault >> ./sage -t --long >> src/sage/rings/function_field/function_field.py # All tests passed >> ./sage -t --long >> src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # All >> tests passed >> ./sage -t --long src/sage/combinat/sf/macdonald.py # All tests >> passed >> ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed >> due to segmentation fault >> ./sage -t --long >> src/sage/algebras/lie_algebras/classical_lie_algebra.py # All >> tests passed >> ./sage -t --long >> src/sage/rings/function_field/function_field_valuation.py # All >> tests passed >> ./sage -t --long src/sage/rings/number_field/number_field.py # >> All tests passed >> ./sage -t --long src/sage/geometry/cone.py # All tests passed >> ./sage -t --long >> src/sage/modular/btquotients/pautomorphicform.py # All tests passed >> ./sage -t --long src/sage/arith/misc.py # All tests passed >> ./sage -t --long src/sage/graphs/strongly_regular_db.pyx # All >> tests passed >> ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure >> len(LE) Expected 1 Got: 50 >> ./sage -t --long >> src/sage/modular/modform_hecketriangle/abstract_space.py # Killed >> due to segmentation fault >> ./sage -t --long src/sage/modular/modform/find_generators.py # >> All tests passed >> ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py >> # Timed out >> ./sage -t --long src/sage/schemes/toric/chow_group.py # All >> tests passed >> ./sage -t --long >> src/sage/groups/matrix_gps/finitely_generated.py # All tests passed >> ./sage -t --long src/sage/rings/function_field/ideal.py # All >> tests passed >> ./sage -t --long src/sage/misc/functional.py # All tests passed >> ./sage -t --long src/sage/rings/number_field/totallyreal_rel.py >> # All tests passed >> ./sage -t --long src/sage/modular/hypergeometric_motive.py # >> All tests passed >> ./sage -t --long src/sage/categories/loop_crystals.py # All >> tests passed >> ./sage -t --long src/sage/algebras/iwahori_hecke_algebra.py # >> All tests passed >> ./sage -t --long src/sage/schemes/curves/projective_curve.py # >> All tests passed >> ./sage -t --long src/sage/modular/overconvergent/genus0.py # >> All tests passed >> ./sage -t --long src/sage/combinat/permutation.py # All tests >> passed >>
Re: [sage-devel] Re: Buiding sage on a Raspberry Pi 4B
Are you sure you don't have a problem with the size of the ram ? You certainly have spool virtual memory partition. I have run some programs on a PI (3) (not Sage), and when the memory was full, I have got some segmentation faults (this should not happen, but..). This was on raspbian, two years ago. Yours, t.d. Le 31/12/2019 à 11:36, Jaap Spies a écrit : > I did run the failing tests! This is really frustrating. > > > ./sage -t --long src/sage/rings/tests.py # Killed due to segmentation > fault NOW: All test passed!! > ./sage -t --long > src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed due to > segmentation fault NOW: All test passed!! > ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to > segmentation fault NOW: All test passed!! > ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure > len(LE) Expected 1 Got: 50 > ./sage -t --long > src/sage/modular/modform_hecketriangle/abstract_space.py # Killed due > to segmentation fault NOW: All test passed!! > ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # > Timed out NOW: All test passed!! in NB 51.16 seconds > ./sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # > Timed out total time 1832.3 seconds NOW: All test passed in 11.74 seconds > ./sage -t --long > src/sage/combinat/designs/evenly_distributed_sets.pyx # Timed out > NOW: All test passed in 8.11 seconds > ./sage -t --long src/sage/modular/modform/tests.py # Times out 1822.7 > seconds NOW: All test passed in 4.12 seconds > ./sage -t --long src/sage/sets/set.py # Times out 1821.5 seconds > NOW: All test passed in 2.08 seconds > ./sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed > ./sage -t --long src/sage/cpython/dict_del_by_value.pyx # 1 doctest > failed > > > On Tuesday, December 31, 2019 at 10:58:38 AM UTC+1, Jaap Spies wrote: > > > > On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote: > > > > I'll make a bash script to do the tests stand alone. > > > > bash test_errors_rc1 >> err.log 2>&1 & > > Resume: > ./sage -t --long src/sage/rings/tests.py # Killed due to > segmentation fault > ./sage -t --long > src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed > due to segmentation fault > ./sage -t --long src/sage/rings/function_field/function_field.py > # All tests passed > ./sage -t --long > src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # All > tests passed > ./sage -t --long src/sage/combinat/sf/macdonald.py # All tests > passed > ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due > to segmentation fault > ./sage -t --long > src/sage/algebras/lie_algebras/classical_lie_algebra.py # All > tests passed > ./sage -t --long > src/sage/rings/function_field/function_field_valuation.py # All > tests passed > ./sage -t --long src/sage/rings/number_field/number_field.py # > All tests passed > ./sage -t --long src/sage/geometry/cone.py # All tests passed > ./sage -t --long > src/sage/modular/btquotients/pautomorphicform.py # All tests passed > ./sage -t --long src/sage/arith/misc.py # All tests passed > ./sage -t --long src/sage/graphs/strongly_regular_db.pyx # All > tests passed > ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure > len(LE) Expected 1 Got: 50 > ./sage -t --long > src/sage/modular/modform_hecketriangle/abstract_space.py # Killed > due to segmentation fault > ./sage -t --long src/sage/modular/modform/find_generators.py # > All tests passed > ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # > Timed out > ./sage -t --long src/sage/schemes/toric/chow_group.py # All > tests passed > ./sage -t --long > src/sage/groups/matrix_gps/finitely_generated.py # All tests passed > ./sage -t --long src/sage/rings/function_field/ideal.py # All > tests passed > ./sage -t --long src/sage/misc/functional.py # All tests passed > ./sage -t --long src/sage/rings/number_field/totallyreal_rel.py > # All tests passed > ./sage -t --long src/sage/modular/hypergeometric_motive.py # All > tests passed > ./sage -t --long src/sage/categories/loop_crystals.py # All > tests passed > ./sage -t --long src/sage/algebras/iwahori_hecke_algebra.py # > All tests passed > ./sage -t --long src/sage/schemes/curves/projective_curve.py # > All tests passed > ./sage -t --long src/sage/modular/overconvergent/genus0.py # All > tests passed > ./sage -t --long src/sage/combinat/permutation.py # All tests passed > ./sage -t --long > src/sage/rings/number_field/number_field_ideal.py # All tests passed > ./sage -t --long > src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx # > All tests passed > ./sage -t --long
[sage-devel] NTL 11.4.2
I just uploaded NTL 11.4.2 to http://www.shoup.net/ntl This fixes a few small, obscure bugs, including one that prevents using the gf2x-1.3 library. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/992c77f6-ebf9-4049-8900-c45c6b89f4ed%40googlegroups.com.
[sage-devel] Re: sage-system-python use in runtime
On Tuesday, December 31, 2019 at 10:57:23 AM UTC-5, John H Palmieri wrote:
>
> On Monday, December 30, 2019 at 9:57:25 PM UTC-8, Isuru Fernando wrote:
>>
>> I'm trying to build sage 9.0.rc1 for conda. [...]
>> In 9.0 some scripts in `src/bin/` use `sage-system-python` which is in
>> `build/bin/`. Shouldn't scripts like `sage-system-python` be used only in
>> scripts under `build`?
>>
>> These scripts use sage-system-python:
>
> sage-coverage
> sage-coverageall
> sage-location
> sage-num-threads.py
> sage-pkg
> sage-pypkg-location
> sage-unzip
>
> Most of these are for development work and/or with package maintenance
> (for example sage-pkg or sage-unzip), and since they are also used in
> various command line options ("./sage -pkg ..."), they should be in
> src/bin. Also, scripts which are supposed to run even if Sage has not been
> built should use sage-system-python, and some of these fit into that
> category (e.g. the packaging scripts, sage-coverage, maybe
> sage-num-threads). Which scripts are causing problems for you?
>
>
See https://trac.sagemath.org/ticket/21559 - "Move sage-the-distribution
scripts from src/bin to build/bin"
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/2e8f9962-612d-4b6f-beb8-e0bb09fd8677%40googlegroups.com.
Re: [sage-devel] Re: sage-system-python use in runtime
Thanks for the reply.
`sage` script calls `sage-location` and `sage-env` which in turn calls
`sage-num-threads.py`. So, only `sage-location` and `sage-num-threads.py`
causes problems.
> Most of these are for development work and/or with package maintenance
(for example sage-pkg or sage-unzip), and since they are also used in
various command line options ("./sage -pkg ..."), they should be in src/bin
If that is the case, then shouldn't `sage-system-python` also be in src/bin?
Isuru
On Tue, Dec 31, 2019 at 9:27 PM John H Palmieri
wrote:
>
>
> On Monday, December 30, 2019 at 9:57:25 PM UTC-8, Isuru Fernando wrote:
>>
>> I'm trying to build sage 9.0.rc1 for conda. For conda what I do is I run,
>> 1. Run configure
>> 2. cp src/bin/* to /bin
>> 3. cp src/ext/* to /share/sage/ext
>> 4. run `python setup.py install` in src
>>
>> This has worked fine until 8.9
>>
>> In 9.0 some scripts in `src/bin/` use `sage-system-python` which is in
>> `build/bin/`. Shouldn't scripts like `sage-system-python` be used only in
>> scripts under `build`?
>>
>> Isuru
>>
>
> These scripts use sage-system-python:
>
> sage-coverage
> sage-coverageall
> sage-location
> sage-num-threads.py
> sage-pkg
> sage-pypkg-location
> sage-unzip
>
> Most of these are for development work and/or with package maintenance
> (for example sage-pkg or sage-unzip), and since they are also used in
> various command line options ("./sage -pkg ..."), they should be in
> src/bin. Also, scripts which are supposed to run even if Sage has not been
> built should use sage-system-python, and some of these fit into that
> category (e.g. the packaging scripts, sage-coverage, maybe
> sage-num-threads). Which scripts are causing problems for you?
>
> --
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/2cf9b9fe-1ba9-48e5-a95b-a5ddc7cc53a8%40googlegroups.com
>
> .
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CA%2B01voN3Exr12fnN2Z1T%2Breo%2BX8uAnM6Mbr0LZaYWVQpAvxeDA%40mail.gmail.com.
[sage-devel] Re: sage-system-python use in runtime
On Monday, December 30, 2019 at 9:57:25 PM UTC-8, Isuru Fernando wrote:
>
> I'm trying to build sage 9.0.rc1 for conda. For conda what I do is I run,
> 1. Run configure
> 2. cp src/bin/* to /bin
> 3. cp src/ext/* to /share/sage/ext
> 4. run `python setup.py install` in src
>
> This has worked fine until 8.9
>
> In 9.0 some scripts in `src/bin/` use `sage-system-python` which is in
> `build/bin/`. Shouldn't scripts like `sage-system-python` be used only in
> scripts under `build`?
>
> Isuru
>
These scripts use sage-system-python:
sage-coverage
sage-coverageall
sage-location
sage-num-threads.py
sage-pkg
sage-pypkg-location
sage-unzip
Most of these are for development work and/or with package maintenance (for
example sage-pkg or sage-unzip), and since they are also used in various
command line options ("./sage -pkg ..."), they should be in src/bin. Also,
scripts which are supposed to run even if Sage has not been built should
use sage-system-python, and some of these fit into that category (e.g. the
packaging scripts, sage-coverage, maybe sage-num-threads). Which scripts
are causing problems for you?
--
John
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/2cf9b9fe-1ba9-48e5-a95b-a5ddc7cc53a8%40googlegroups.com.
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
Am Dienstag, 31. Dezember 2019 11:50:08 UTC+1 schrieb Volker Braun: > > Which hardware are you using, and how long does it take to bulid and run > the tests? > > On Tuesday, December 31, 2019 at 12:14:28 AM UTC+1, Timo Kaufmann wrote: >> >> For what it's worth, I regularly build and test sage-on-nixos on aarch64. >> The testsuite shows no issues, except some transient timeouts which may or >> may not be caused by the architecture. >> > Our community build box[1] which has 64 (relatively weak) cores and plenty of RAM. So not really comparable with a raspberry pi, but still ARM/aarch64 (not sure if OP is using their rpi with a 32bit or 64 bit OS). Because of all the parallelism, building sagelib takes maybe 10-15 minutes and the test suite something under half an hour I think. Most of the dependencies are taken from the nix binary caches (where they have been built on similar aarch64 machines), or they are built locally if they're not available in the caches yet. [1] https://github.com/nix-community/aarch64-build-box -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/fe49453a-fdb9-41d8-85c8-217eb5f6937a%40googlegroups.com.
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
Which hardware are you using, and how long does it take to bulid and run the tests? On Tuesday, December 31, 2019 at 12:14:28 AM UTC+1, Timo Kaufmann wrote: > > For what it's worth, I regularly build and test sage-on-nixos on aarch64. > The testsuite shows no issues, except some transient timeouts which may or > may not be caused by the architecture. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/47b989f5-6156-445d-8e9a-381dc4cd7aa5%40googlegroups.com.
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
I did run the failing tests! This is really frustrating. ./sage -t --long src/sage/rings/tests.py # Killed due to segmentation fault NOW: All test passed!! ./sage -t --long src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed due to segmentation fault NOW: All test passed!! ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to segmentation fault NOW: All test passed!! ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure len(LE) Expected 1 Got: 50 ./sage -t --long src/sage/modular/modform_hecketriangle/abstract_space.py # Killed due to segmentation fault NOW: All test passed!! ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # Timed out NOW: All test passed!! in NB 51.16 seconds ./sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Timed out total time 1832.3 seconds NOW: All test passed in 11.74 seconds ./sage -t --long src/sage/combinat/designs/evenly_distributed_sets.pyx # Timed out NOW: All test passed in 8.11 seconds ./sage -t --long src/sage/modular/modform/tests.py # Times out 1822.7 seconds NOW: All test passed in 4.12 seconds ./sage -t --long src/sage/sets/set.py # Times out 1821.5 seconds NOW: All test passed in 2.08 seconds ./sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed ./sage -t --long src/sage/cpython/dict_del_by_value.pyx # 1 doctest failed On Tuesday, December 31, 2019 at 10:58:38 AM UTC+1, Jaap Spies wrote: > > > > On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote: >> >> >> >> I'll make a bash script to do the tests stand alone. >> >> >>> > bash test_errors_rc1 >> err.log 2>&1 & > > Resume: > ./sage -t --long src/sage/rings/tests.py # Killed due to segmentation > fault > ./sage -t --long src/sage/schemes/elliptic_curves/ell_rational_field.py # > Killed due to segmentation fault > ./sage -t --long src/sage/rings/function_field/function_field.py # All > tests passed > ./sage -t --long > src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # All tests > passed > ./sage -t --long src/sage/combinat/sf/macdonald.py # All tests passed > ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to > segmentation fault > ./sage -t --long src/sage/algebras/lie_algebras/classical_lie_algebra.py > # All tests passed > ./sage -t --long > src/sage/rings/function_field/function_field_valuation.py # All tests > passed > ./sage -t --long src/sage/rings/number_field/number_field.py # All tests > passed > ./sage -t --long src/sage/geometry/cone.py # All tests passed > ./sage -t --long src/sage/modular/btquotients/pautomorphicform.py # All > tests passed > ./sage -t --long src/sage/arith/misc.py # All tests passed > ./sage -t --long src/sage/graphs/strongly_regular_db.pyx # All tests > passed > ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure len(LE) > Expected 1 Got: 50 > ./sage -t --long src/sage/modular/modform_hecketriangle/abstract_space.py > # Killed due to segmentation fault > ./sage -t --long src/sage/modular/modform/find_generators.py # All tests > passed > ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # Timed > out > ./sage -t --long src/sage/schemes/toric/chow_group.py # All tests passed > ./sage -t --long src/sage/groups/matrix_gps/finitely_generated.py # All > tests passed > ./sage -t --long src/sage/rings/function_field/ideal.py # All tests > passed > ./sage -t --long src/sage/misc/functional.py # All tests passed > ./sage -t --long src/sage/rings/number_field/totallyreal_rel.py # All > tests passed > ./sage -t --long src/sage/modular/hypergeometric_motive.py # All tests > passed > ./sage -t --long src/sage/categories/loop_crystals.py # All tests passed > ./sage -t --long src/sage/algebras/iwahori_hecke_algebra.py # All tests > passed > ./sage -t --long src/sage/schemes/curves/projective_curve.py # All tests > passed > ./sage -t --long src/sage/modular/overconvergent/genus0.py # All tests > passed > ./sage -t --long src/sage/combinat/permutation.py # All tests passed > ./sage -t --long src/sage/rings/number_field/number_field_ideal.py # All > tests passed > ./sage -t --long > src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx # All tests > passed > ./sage -t --long src/sage/geometry/triangulation/element.py # All tests > passed > ./sage -t --long src/sage/schemes/elliptic_curves/period_lattice.py # > All tests passed > ./sage -t --long src/sage/schemes/elliptic_curves/ell_field.py # All > tests passed > ./sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Timed > out total time 1832.3 seconds > ./sage -t --long src/sage/rings/number_field/galois_group.py # All tests > passed > ./sage -t --long src/sage/rings/valuation/limit_valuation.py # All tests > passed > ./sage -t --long src/sage/combinat/e_one_star.py # All tests passed > ./sage -t --long src/sage/combinat/designs/latin_squares.py
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
On Monday, December 30, 2019 at 11:21:34 PM UTC+1, Jaap Spies wrote: > > > > I'll make a bash script to do the tests stand alone. > > >> bash test_errors_rc1 >> err.log 2>&1 & Resume: ./sage -t --long src/sage/rings/tests.py # Killed due to segmentation fault ./sage -t --long src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed due to segmentation fault ./sage -t --long src/sage/rings/function_field/function_field.py # All tests passed ./sage -t --long src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # All tests passed ./sage -t --long src/sage/combinat/sf/macdonald.py # All tests passed ./sage -t --long src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to segmentation fault ./sage -t --long src/sage/algebras/lie_algebras/classical_lie_algebra.py # All tests passed ./sage -t --long src/sage/rings/function_field/function_field_valuation.py # All tests passed ./sage -t --long src/sage/rings/number_field/number_field.py # All tests passed ./sage -t --long src/sage/geometry/cone.py # All tests passed ./sage -t --long src/sage/modular/btquotients/pautomorphicform.py # All tests passed ./sage -t --long src/sage/arith/misc.py # All tests passed ./sage -t --long src/sage/graphs/strongly_regular_db.pyx # All tests passed ./sage -t --long src/sage/structure/coerce_dict.pyx # 1 failure len(LE) Expected 1 Got: 50 ./sage -t --long src/sage/modular/modform_hecketriangle/abstract_space.py # Killed due to segmentation fault ./sage -t --long src/sage/modular/modform/find_generators.py # All tests passed ./sage -t --long src/sage/modular/modform/cuspidal_submodule.py # Timed out ./sage -t --long src/sage/schemes/toric/chow_group.py # All tests passed ./sage -t --long src/sage/groups/matrix_gps/finitely_generated.py # All tests passed ./sage -t --long src/sage/rings/function_field/ideal.py # All tests passed ./sage -t --long src/sage/misc/functional.py # All tests passed ./sage -t --long src/sage/rings/number_field/totallyreal_rel.py # All tests passed ./sage -t --long src/sage/modular/hypergeometric_motive.py # All tests passed ./sage -t --long src/sage/categories/loop_crystals.py # All tests passed ./sage -t --long src/sage/algebras/iwahori_hecke_algebra.py # All tests passed ./sage -t --long src/sage/schemes/curves/projective_curve.py # All tests passed ./sage -t --long src/sage/modular/overconvergent/genus0.py # All tests passed ./sage -t --long src/sage/combinat/permutation.py # All tests passed ./sage -t --long src/sage/rings/number_field/number_field_ideal.py # All tests passed ./sage -t --long src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx # All tests passed ./sage -t --long src/sage/geometry/triangulation/element.py # All tests passed ./sage -t --long src/sage/schemes/elliptic_curves/period_lattice.py # All tests passed ./sage -t --long src/sage/schemes/elliptic_curves/ell_field.py # All tests passed ./sage -t --long src/sage/modular/arithgroup/congroup_gammaH.py # Timed out total time 1832.3 seconds ./sage -t --long src/sage/rings/number_field/galois_group.py # All tests passed ./sage -t --long src/sage/rings/valuation/limit_valuation.py # All tests passed ./sage -t --long src/sage/combinat/e_one_star.py # All tests passed ./sage -t --long src/sage/combinat/designs/latin_squares.py # All tests passed ./sage -t --long src/sage/combinat/designs/evenly_distributed_sets.pyx # Timed out ./sage -t --long src/sage/geometry/polyhedron/combinatorial_polyhedron/polyhedron_face_lattice.pyx # All tests passed ./sage -t --long src/sage/calculus/wester.py # All tests passed ./sage -t --long src/sage/groups/artin.py # All tests passed ./sage -t --long src/sage/symbolic/ring.pyx # All tests passed ./sage -t --long src/sage/structure/coerce.pyx # All tests passed ./sage -t --long src/sage/modular/modsym/tests.py # All tests passed ./sage -t --long src/sage/modular/modform/ambient_g1.py # All tests passed ./sage -t --long src/sage/tests/books/judson-abstract-algebra/fields-sage.py # All tests passed ./sage -t --long src/sage/rings/polynomial/multi_polynomial_element.py # All tests passed ./sage -t --long src/sage/repl/preparse.py # All tests passed ./sage -t --long src/sage/tests/book_stein_modform.py # All tests passed ./sage -t --long src/sage/modular/modform/tests.py # Times out 1822.7 seconds ./sage -t --long src/sage/homology/simplicial_complex_morphism.py # All tests passed ./sage -t --long src/sage/algebras/quaternion_algebra_element.py # All tests passed ./sage -t --long src/sage/structure/factorization.py # All tests passed ./sage -t --long src/sage/sets/set.py # Times out 1821.5 seconds ./sage -t --long src/sage/quadratic_forms/quadratic_form__split_local_covering.py # All tests passed ./sage -t --long src/sage/misc/weak_dict.pyx # 11 doctests failed ./sage -t --long src/sage/modular/modform/eis_series.py #
