#2732: cython in Debian build doesn't have the right include paths
[Reviewed by Jeroen Demeyer]
#5943: Sage 3.4.2.a0: len(prime_range(2^50)) segfaults [Reviewed by
Michael Orlitzky, Keshav Kini, Volker Braun]
#11844: Race condition in building MPIR/yasm [Reviewed by Leif Leonhardy]
#12315: OS X Lion: pari fails self tests [Reviewed by John Palmieri]
#12319: OS X Lion: gsl fails self tests [Reviewed by John Palmieri]
#12424: OS X Lion: symmetrica doesn't work [Reviewed by John Palmieri]
#12765: MPIR doesn't compile with GCC-4.7.0 on ia64 [Reviewed by Jeroen
Demeyer]
#12782: When building GCC, build MPIR without the C++ interface
[Reviewed by Jeroen Demeyer]
Merged in sage-5.0.rc0:
#5859: Michael Orlitzky: sage -coverageall fails on directories with
zero tests [Reviewed by André Apitzsch]
#8119: Robert Bradshaw: Rename change the hash value of some objects
[Reviewed by Florent Hivert, Nicolas M. Thiéry, Nicolas Borie]
#11616: Leif Leonhardy, Jeroen Demeyer: Upgrade MPIR to a more recent
upstream release [Reviewed by Jeroen Demeyer, Leif Leonhardy, Volker Braun]
#12272: Jeroen Demeyer: More # long time additions [Reviewed by Georg S.
Weber]
#12812: Andrey Novoseltsev: Bug in summation of toric divisors [Reviewed
by Volker Braun]
#12830: Leif Leonhardy: Work around GCC 4.7.0 bug on ia64 and improve
the GMP-ECM spkg [Reviewed by Jeroen Demeyer]
#12833: Nathann Cohen: Crashes and doctests problems with Gurobi
[Reviewed by John Perry]
#12837: Leif Leonhardy: MPFR doesn't compile with GCC-4.7.0 on ia64
[Reviewed by Volker Braun]
#12857: Jeroen Demeyer: Split off Graphics class from plot.py [Reviewed
by Benjamin Jones, Florent Hivert]
#12888: David Coudert: Set new default parameters for RandomGNP
[Reviewed by Nathann Cohen]
I haven't really looked into the failures yet other than the cmdline
ones. IPython complains about my ipythonrc. This complaint goes away
if I let sage's copy of ipython (0.10.2) make its own dot_ipython
folder, instead of using my system one, which is generated by my
system install (0.12.1) that I frequently use. The other failure is
regarding a hg extension I have, so that is probably not the fault of
sage.
On Wed, May 2, 2012 at 2:54 PM, Benjamin Jones <benjaminfjo...@gmail.com> wrote:
> On Wed, May 2, 2012 at 2:02 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
>> Dear Sage lovers,
>> Please build, test, and report! We'd love to hear about your
>> experiences with this release.
> Sage-5.0.rc0 builds and passes all tests (make ptestlong) on my fedora
> 16 x86_64 machine:
>> uname -a
> Linux kimchi.homenetwork 3.3.2-6.fc16.x86_64 #1 SMP Sat Apr 21
> 12:43:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Also, regarding #12857, I looked through the live documentation on 2D
> / 3D plotting and everything looks good, as expected.
> --
> Benjamin Jones
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 3051.5 seconds
0 jan@snapperkob:~/src/sage-source-builds/sage-5.0.rc0$uname -a
Linux snapperkob 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
0 jan@snapperkob:~/src/sage-source-builds/sage-5.0.rc0$lsb_release -d
Description: Ubuntu 12.04 LTS
0 jan@snapperkob:~/src/sage-source-builds/sage-5.0.rc0$grep name
/proc/cpuinfo
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Built successfully on i386/i686
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:c ore-3.1-noarch:core-3.2-ia32:core-3.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric
Only env variables set:
MAKE=make -j2
SAGE_PARALLEL_SPKG_BUILD=yes
All ./sage -testall -long passed except:
sage -t -long -force_lib "devel/sage/sage/misc/randstate.pyx" # Time out
sage -t -long -force_lib "devel/sage/sage/interacts/debugger.py" #
Time out
sage -t -long -force_lib "devel/sage/sage/interfaces/expect.py" #
Time out
sage -t -long -force_lib "devel/sage/sage/interfaces/sage0.py" #
Time out
sage -t -long -force_lib "devel/sage/sage/interfaces/psage.py" #
Time out
sage -t -long -force_lib "devel/sage/sage/tests/startup.py" # Time
out
On Wed, May 2, 2012 at 3:02 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Running ./sage -testall -long, I get:
<snip>
----------------------------------------------------------------------
The following tests failed:
sage -t -long -force_lib
"devel/sage/doc/en/installation/source.rst" # Time out
sage -t -long -force_lib "devel/sage/sage/misc/sagedoc.py"
sage -t -long -force_lib
"devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py" # Time
out
Total time for all tests: 68027.9 seconds
Please see /home/hdevalence/.sage//tmp/test.log for the complete log
from this test.
The test that didn't time out but just failed has the following description in
the log file:
sage -t -long -force_lib "devel/sage/sage/misc/sagedoc.py"·
**********************************************************************
File "/home/hdevalence/code/sage-5.0.rc0/devel/sage/sage/misc/sagedoc.py",
line 22:
sage: for line in open(docfilename):
if "#sage.symbolic.expression.Expression.N" in line:
print line
Exception raised:
Traceback (most recent call last):
File "/home/hdevalence/code/sage-5.0.rc0/local/bin/ncadoctest.py",
line 1231, in run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/home/hdevalence/code/sage-5.0.rc0/local/bin/sagedoctest.py",
line 38, in run_one_example
OrigDocTestRunner.run_one_example(self, test, example,
filename, compileflags)
File "/home/hdevalence/code/sage-5.0.rc0/local/bin/ncadoctest.py",
line 1172, in run_one_example
compileflags, 1) in test.globs
File "<doctest __main__.example_0[3]>", line 1, in <module>
for line in open(docfilename):###line 22:
sage: for line in open(docfilename):
IOError: [Errno 2] No such file or directory:
'/home/hdevalence/code/sage-5.0.rc0/devel/sage/doc/output/html/en/reference /sage/symbolic/expression.html'
**********************************************************************
File "/home/hdevalence/code/sage-5.0.rc0/devel/sage/sage/misc/sagedoc.py",
line 576:
sage: 'abvar/homology' in _search_src_or_doc('doc', 'homology',
'variety', interact=False) # long time (4s on sage.math, 2012)
Expected:
True
Got:
False
**********************************************************************
2 items had failures:
1 of 5 in __main__.example_0
1 of 8 in __main__.example_8
***Test Failed*** 2 failures.
For whitespace errors, see the file /home/hdevalence/.sage//tmp/sagedoc_25648.py
[518.5 s]
On Friday, May 4, 2012 12:27:33 PM UTC-7, Henry de Valence wrote:
> On Wed, May 2, 2012 at 3:02 AM, Jeroen Demeyer wrote: > > Please build, test, and report! We'd love to hear about your > > experiences with this release.
> <snip> > ---------------------------------------------------------------------- > The following tests failed:
> sage -t -long -force_lib > "devel/sage/doc/en/installation/source.rst" # Time out > sage -t -long -force_lib "devel/sage/sage/misc/sagedoc.py" > sage -t -long -force_lib > "devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py" # Time > out > Total time for all tests: 68027.9 seconds > Please see /home/hdevalence/.sage//tmp/test.log for the complete log > from this test.
> The test that didn't time out but just failed has the following > description in > the log file:
The ensuing error messages make it look like the documentation didn't build. Is that true?
On Fri, May 4, 2012 at 4:59 PM, John H Palmieri <jhpalmier...@gmail.com> wrote:
> On Friday, May 4, 2012 12:27:33 PM UTC-7, Henry de Valence wrote:
>> On Wed, May 2, 2012 at 3:02 AM, Jeroen Demeyer wrote:
>> > Please build, test, and report! We'd love to hear about your
>> > experiences with this release.
>> Running ./sage -testall -long, I get:
> What sort of machine, OS, etc.?
The machine is an EEE PC X101 (Intel Atom N435 @1.33 GHz, 2 GB RAM)
running 64-bit Debian Squeeze. But Sage is on a microSD card instead of on
the internal SSD, because with an 8GB SSD, there's not a lot of room for
multiple Sage installs + all the system stuff.
>> <snip>
>> ----------------------------------------------------------------------
>> The following tests failed:
>> sage -t -long -force_lib
>> "devel/sage/doc/en/installation/source.rst" # Time out
>> sage -t -long -force_lib "devel/sage/sage/misc/sagedoc.py"
>> sage -t -long -force_lib
>> "devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py" # Time
>> out
>> Total time for all tests: 68027.9 seconds
>> Please see /home/hdevalence/.sage//tmp/test.log for the complete log
>> from this test.
>> The test that didn't time out but just failed has the following
>> description in
>> the log file:
> The ensuing error messages make it look like the documentation didn't build.
> Is that true?
I'm not sure -- when I run the Sage IPython, I can get documentation,
so it would appear that the documentation was built.
> But Sage is on a microSD card instead
> of on the internal SSD, because with an 8GB SSD, there's not a lot of
> room for multiple Sage installs + all the system stuff.
Do you have any idea of how much overlap there is between all those
sage installations?
On Sun, May 6, 2012 at 4:33 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2012-05-06 19:53, Henry de Valence wrote:
>> I'm not sure -- when I run the Sage IPython, I can get documentation,
>> so it would appear that the documentation was built.
> Could you attach the file $SAGE_ROOT/dochtml.log
> That way, we can check.
Exception occurred:
File "/home/hdevalence/code/sage-5.0.rc0/local/lib/python/subprocess.py",
line 1130, in _execute_child
self.pid = os.fork()
OSError: [Errno 12] Cannot allocate memory
The full traceback has been saved in /tmp/sphinx-err-GAIaQW.log, if
you want to report the issue to the developers.
So maybe this is just an issue with my machine? But it has around 3GB
of memory + swap, so it seems a bit strange that it would run out of
memory.
Is there a way to redo just this part so I can watch what happens?
> So maybe this is just an issue with my machine? But it has around 3GB
> of memory + swap, so it seems a bit strange that it would run out of
> memory.
Sage needs about 2.5GB of memory to build the documentation, so it's not
that strange.
> Is there a way to redo just this part so I can watch what happens?
If you look at second message in this thread you will see that I've
reported a somehow similar behavior. However, there was no exception on my
machine (maybe because is 64 bit and the swap space was not exhausted, yet).
cpuinfo:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
stepping : 6
microcode : 0x44
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow
bogomips : 4266.83
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
And ram:
~/Installations/sage-5.0.rc0» free -m
total used free shared buffers cached
Mem: 3954 1457 2497 0 70 692
-/+ buffers/cache: 694 3260
Swap: 2231 0 2231
uname:
~/Installations/sage-5.0.rc0» uname -a
Linux ub2 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
And I set the following CFLAGS, CXXFLAGS (and MAKE is empty):
~/Installations/sage-5.0.rc0» export CFLAGS="-march=native -O3 -pipe"
~/Installations/sage-5.0.rc0» export CXXFLAGS="${CFLAGS}"
> #2732: cython in Debian build doesn't have the right include paths > [Reviewed by Jeroen Demeyer] > #5943: Sage 3.4.2.a0: len(prime_range(2^50)) segfaults [Reviewed by > Michael Orlitzky, Keshav Kini, Volker Braun] > #11844: Race condition in building MPIR/yasm [Reviewed by Leif Leonhardy] > #12315: OS X Lion: pari fails self tests [Reviewed by John Palmieri] > #12319: OS X Lion: gsl fails self tests [Reviewed by John Palmieri] > #12424: OS X Lion: symmetrica doesn't work [Reviewed by John Palmieri] > #12765: MPIR doesn't compile with GCC-4.7.0 on ia64 [Reviewed by Jeroen > Demeyer] > #12782: When building GCC, build MPIR without the C++ interface > [Reviewed by Jeroen Demeyer]
> Merged in sage-5.0.rc0:
> #5859: Michael Orlitzky: sage -coverageall fails on directories with > zero tests [Reviewed by André Apitzsch] > #8119: Robert Bradshaw: Rename change the hash value of some objects > [Reviewed by Florent Hivert, Nicolas M. Thiéry, Nicolas Borie] > #11616: Leif Leonhardy, Jeroen Demeyer: Upgrade MPIR to a more recent > upstream release [Reviewed by Jeroen Demeyer, Leif Leonhardy, Volker > Braun] > #12272: Jeroen Demeyer: More # long time additions [Reviewed by Georg S. > Weber] > #12812: Andrey Novoseltsev: Bug in summation of toric divisors [Reviewed > by Volker Braun] > #12830: Leif Leonhardy: Work around GCC 4.7.0 bug on ia64 and improve > the GMP-ECM spkg [Reviewed by Jeroen Demeyer] > #12833: Nathann Cohen: Crashes and doctests problems with Gurobi > [Reviewed by John Perry] > #12837: Leif Leonhardy: MPFR doesn't compile with GCC-4.7.0 on ia64 > [Reviewed by Volker Braun] > #12857: Jeroen Demeyer: Split off Graphics class from plot.py [Reviewed > by Benjamin Jones, Florent Hivert] > #12888: David Coudert: Set new default parameters for RandomGNP > [Reviewed by Nathann Cohen]
> And I set the following CFLAGS, CXXFLAGS (and MAKE is empty):
> ||
> ~/Installations/sage-5.0.rc0 exportCFLAGS="-march=native -O3 -pipe"
> ~/Installations/sage-5.0.rc0 exportCXXFLAGS="${CFLAGS}"
What if you don't use -march=native? Could you recompile mpir and mpfr
with just "-O3 -pipe" (or other variations of CFLAGS)?
> On 2012-05-09 09:34, P Purkayastha wrote:
> > And I set the following CFLAGS, CXXFLAGS (and MAKE is empty):
> > ||
> > ~/Installations/sage-5.0.rc0»exportCFLAGS="-march=native -O3 -pipe"
> > ~/Installations/sage-5.0.rc0»exportCXXFLAGS="${CFLAGS}"
> What if you don't use -march=native? Could you recompile mpir and mpfr
> with just "-O3 -pipe" (or other variations of CFLAGS)?
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to
> sage-devel+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org
> On Wed, May 9, 2012 at 3:56 PM, Jeroen Demeyer <jdeme...@cage.ugent.be
> <mailto:jdeme...@cage.ugent.be>> wrote:
> On 2012-05-09 09:52, P Purkayastha wrote:
> > Actually, I already tried that. It fails in the same way.
> And without setting any CFLAGS
> That's what I meant. Without having set anything. Just plain "make."
It seems the CFLAGS were cached somewhere (I had run in a separate terminal too, so it wasn't in the env). Even a "make clean" couldn't get rid of the CFLAGS settings. I removed the whole sage directory and unpacked a fresh one. Simple "make" is running now, and has passed the MPFR package.
