On SageMathCloud, built from source, passes long tests ("ptestlong").
https://cloud.sagemath.com/projects/53b77207-8614-4086-a032-432af4b4cdbd/files/sage-dev-images/
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
On Jul 22, 2015, at 01:17 , Volker Braun wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
Built from the tarball on OSX 10.6.8 (Dual 6-core Xeons) and 1
I vaguely remember having similar issues on gcc110 and another machine
where I use something like make -j64 or 80.
It fails first and then succeeds on second run.
And I remember something about ppl (or was it palp? similar letters...)
failing.
Maybe make is not robust enough?
Next time it happens
The palp failure disappeared in the two subsequent builds I have
done one with host gcc and one with sage’s gcc. Not sure what went wrong the
first time.
sympow’s problem has persisted all throughout.
cpuinfo:
[frb15@hp1 sage-6.8.rc1]$ tail -27 /proc/cpuinfo
processor : 111
vendor_id
What kind of CPU? It seems pretty clear that palp is being miscompiled for
that target.
Can you search for the actual error in the log, this should tell us more.
On Thursday, July 23, 2015 at 4:44:32 AM UTC+2, François wrote:
>
> Some other thing of interest that came up during the build.
> Th
Some other thing of interest that came up during the build.
This machine has a total of 112 (one hundred and twelve) cores.
Doing "make -j112" is useless because it starves i/o considerably,
so I settled on 20.
I am at my third build on this machine (not counting a
sage-on-gentoo-prefix build) and
I could do another build with native gcc to check again but
I still have these after forcing sage's gcc:
sage -t --long --warn-long 97.3
src/sage/schemes/elliptic_curves/ell_rational_field.py # 2 doctests failed
sage -t --long --warn-long 97.3 src/sage/lfunctions/sympow.py # 4
doctests failed
But Scientific Linux is (like Centos) a recompiled Redhat, so we should
have that covered.
On Wednesday, July 22, 2015 at 8:43:24 PM UTC+2, François wrote:
>
> Feels unlikely as someone would have suffered from that before you would
> think. I am suspecting some miscompilation and will force s
Feels unlikely as someone would have suffered from that before you would
think. I am suspecting some miscompilation and will force sage’s gcc.
François
> On 23/07/2015, at 01:55, Wilfried Lübbe wrote:
>
>
>
> Am Mittwoch, 22. Juli 2015 13:31:26 UTC+2 schrieb François:
>
> sage -t --long --wa
Am Mittwoch, 22. Juli 2015 13:31:26 UTC+2 schrieb François:
>
>
> sage -t --long --warn-long 314.9
> src/sage/geometry/polyhedron/palp_database.py # 20 doctests failed
>
These failures could be caused by http://trac.sagemath.org/ticket/17398.
Wilfried
--
You received this message because
Scientific linux 7.1 x86_64:
--
sage -t --long --warn-long 314.9
src/sage/schemes/elliptic_curves/ell_rational_field.py # 2 doctests failed
sage -t --long --warn-long 314.9 src/sage/lfunctions/sympow.py # 4 doctests
failed
sage
As always, you can get the latest beta version from the "develop" git
branch. Alternatively, the self-contained source tarball is at
http://www.sagemath.org/download-latest.html
3648190 Updated Sage version to 6.8.rc1
707189c Trac #18924: Missing dependencies file in package arb
03a4c69 Trac #16
12 matches
Mail list logo