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
>
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)
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
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
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
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/`.
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),
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
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
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
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
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
12 matches
Mail list logo