>> I used the "for loop" from earlier in the thread on Mac OS X (both 10.6.8
>> and 10.7.4). In both cases, all worked w/o crashing.
>>
>> Does this happen rarely, sometimes, frequently?
>
> It occurred for me about 4 times interactively while working on
> research yesterday. Anyway, thanks for
On Fri, Jun 8, 2012 at 10:58 AM, Justin C. Walker wrote:
>
> On Jun 7, 2012, at 16:19 , William Stein wrote:
>
>> Hi Sage-Devel,
>>
>> I'm randomly running into segfaults when multiplying matrices over the
>> integers, in the course of doing basic modular symbols calculations.
>> For example, some
On Jun 7, 2012, at 16:19 , William Stein wrote:
> Hi Sage-Devel,
>
> I'm randomly running into segfaults when multiplying matrices over the
> integers, in the course of doing basic modular symbols calculations.
> For example, sometimes (but not always), this crashes:
>
> sage: M = ModularSymbol
Hi Sage-Devel,
I'm randomly running into segfaults when multiplying matrices over the
integers, in the course of doing basic modular symbols calculations.
For example, sometimes (but not always), this crashes:
sage: M = ModularSymbols(389,sign=0).cuspidal_submodule().decomposition()[0]
...
/Users
Le dimanche 27 mai, Juanjo a écrit:
> A patch has been uploaded to ECL's bug tracker. Please report whether
> it works for you.
I see the message about it in the bug tracker, but no file is
attached.
I'll test as soon as I can.
Snark on #sagemath
--
To post to this group, send an email to sage
A patch has been uploaded to ECL's bug tracker. Please report whether it
works for you.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://gr
On Sunday, May 27, 2012 3:19:51 PM UTC+2, Snark wrote:
>
> Hence when I wrote that maxima() and python didn't matter -- they
> don't, since I don't run them at any point. I only run
> maxima-the-sofware on top of ECL.
> On ARM, Maxima 5.26.0 using Lisp ECL 11.1.1 gives:
> (%i1) 1.7e17;
> (%o1)
Le dimanche 27 mai, Juanjo a écrit:
> Your test is checking that data can be converted from python to
> Maxima and viceversa. This test is built on these assumptions
>
> 1) The python code can convert from "double float" to Maxima's
> representation accurately.
> 2) Maxima can produce an accurate
On Sunday, May 27, 2012 1:39:40 PM UTC+2, Snark wrote:
>
> In fact it doesn't matter what maxima() returns and how python converts
> it : I could check that within maxima itself, there is a difference
> between what I get on ARM (1.69...9e+17) and on x86_64 (1.7e+17).
>
So what? printf() will a
Le dimanche 27 mai, Juanjo a écrit:
> It also matters what maxima() returns (a string?) and how python
> converts it to floating point number: ECL uses a method to match
> printed representation and floating point numbers which is NOT the C
> library, for this has proven to be buggy (to say the lea
BTW, I rarely read this group. If you need some quick answer, please Cc
your message to me or contribute to the bug report.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more op
On Saturday, May 26, 2012 9:45:39 PM UTC+2, Snark wrote:
>
> Le dimanche 20 mai, Julien Puydt a écrit:
> > sage -t --long -force_lib
> > devel/sage/sage/interfaces/maxima_abstract.py
> > **
> > File
> >
> "/home/jpuydt/sag
Le dimanche 20 mai, Julien Puydt a écrit:
> sage -t --long -force_lib
> devel/sage/sage/interfaces/maxima_abstract.py
> **
> File
> "/home/jpuydt/sage-5.0/devel/sage-main/sage/interfaces/maxima_abstract.py",
> line 1595: sage: flo
Hi,
it compiles (so I have a box on which sage 5.0 does!), from the
pristine tarball!
Not all unit tests pass, though ; errors are the following :
sage -t --long -force_lib devel/sage/sage/interfaces/maxima_abstract.py
**
File
Le mercredi 16 mai, Jeroen Demeyer a écrit:
> Merged in sage-5.0.rc1:
>
> #12898: Jeroen Demeyer: Update top-level README.txt [Reviewed by
> William Stein, Karl-Dieter Crisman, David Kirkby, Martin Raum]
> #12899: Jeroen Demeyer: Update the "Install from Source Code" docs for
> sage-5.0 [Reviewed
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).
Nick
--
To post to this group, send an email to sage-devel@googlegroups.com
On 2012-05-07 04:45, Henry de Valence wrote:
> 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
On Sun, May 6, 2012 at 4:33 PM, Jeroen Demeyer 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 ca
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.
--
To post to this group, send an email to sage-deve
Le dimanche 06 mai, Henry de Valence a écrit:
> 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 installat
On Fri, May 4, 2012 at 4:59 PM, John H Palmieri 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.
>>
>> Ru
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, O
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:
--
The following tests failed:
On Wed, May 2, 2012 at 5:02 PM, Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc0.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.
Hi
On 2 May 2012 09:02, Jeroen Demeyer wrote:
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0.tar
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
>
make -j3 ptestlong on Ubuntu 12.04:
---
On Wed, May 2, 2012 at 5:02 PM, Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc0.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.
Ok, finished building + testing on my Funtoo x86_64 install w/ sandy
bridge and gcc-4.6.2:
The following tests failed:
sage -t --long -force_lib devel/sage/sage/interfaces/expect.py # 1
doctests failed
sage -t --long -force_lib devel/sage/sage/tests/cmdline.py # 2
doctests fai
On Wed, May 2, 2012 at 2:02 AM, Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc0.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.
I just built sage-5.0.rc0 on FreeBSD. When I do make test, one of the
test failures is puzzling me:
sage -t -force_lib "devel/sage/sage/tests/startup.py"
**
File
"/usr/home/stephen/sage-devel/work/sage-5.0.rc0/devel/sage/sage
On Wed, May 2, 2012 at 3:02 AM, Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc0.
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Same doctest errors with 'make ptest' as for beta14:
$ uname -a
Darwin lacim-macpro-02 10
Well, on my machine is eating all my memory (I believe is near the end,
since the log file is already 24 MB).
I have attached the tree of processes and the command used to start each
one. As it is there for a while, it may be a GCC bug .
Ubuntu 11.10 - 64-bit
> 4 GB memory
>
> Architecture: x86_6
Dear Sage lovers,
We're releasing Sage 5.0.rc0.
Source archive:
http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0.tar
Upgrade path:
http://boxen.math.washington.edu/home/release/sage-5.0.rc0/sage-5.0.rc0/
The source and upgrade path can also be found on the mirror networ
Hello!
I'm reporting here the compilation results on:
> Ubuntu 11.10 - 64-bit
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 2
> On-line CPU(s) list: 0,1
> Thread(s) per core: 1
> Core(s) per socket: 2
> CPU socket(s): 1
> NUMA node(s): 1
> Vendor ID
On 2012-04-29 18:41, Rajeev Singh wrote:
> Hi,
>
> I got the following error while compiling sage-5.0.beta14.
Could you please post the contents of
spkg/logs/mpir-2.1.3.p9.log
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Hi,
I got the following error while compiling sage-5.0.beta14. I had got
the same error with sage-5.0.beta13 which I reported earlier.
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./x86_64
-I/home/rajeev/bin/sage-5.0.beta14/local/include
-I/home/rajeev/bin/sage-5.0.beta14/local/include -march=na
Le samedi 28 avril, Julien Puydt a écrit:
> I'll post updates about the results of make ptestlong when I'll have
> them (tomorrow).
Here they are :
--
The following tests failed:
sage -t --long -force_lib
devel/
Hi,
here is a new report on the status of sage on ARM (ubuntu) : I just got
a successful build of 5.0.beta14 -- no patch, no special spkg, just the
bare, unadorned, ugly-as-can-be 5.0.beta14.
So 5.0.beta14 will stay in History as the first sage version to compile
as-is on ARM :-)
I'll post updat
Hi,
I got the following error while compiling sage-5.0.beta13 -
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./x86_64
-I/home/rajeev/bin/sage-5.0.beta13/local/include
-I/home/rajeev/bin/sage-5.0.beta13/local/include -march=native -g -O3
-fPIC -MT libecm_la-mul_fft.lo -MD -MP -MF .deps/libecm_la-m
On Wed, Apr 11, 2012 at 10:10:28AM +0200, Jeroen Demeyer wrote:
> On 2012-04-11 09:08, Florent Hivert wrote:
> > I haven't yet bissected the problem. I'd like to make it a blocker for the
> > next release.
> Go ahead. I can always lower the priority again :-)
First of all, can you confirm the pro
On 2012-04-11 09:08, Florent Hivert wrote:
> I haven't yet bissected the problem. I'd like to make it a blocker for the
> next release.
Go ahead. I can always lower the priority again :-)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
Hi Jeroen,
On Wed, Apr 11, 2012 at 08:51:35AM +0200, Jeroen Demeyer wrote:
> The current plan is to release sage-5.0.beta14 merging most or all of
> the tickets which are currently positively reviewed.
>
> After that, no more patches adding new features, only bugfixes. So I
> guess there m
The current plan is to release sage-5.0.beta14 merging most or all of
the tickets which are currently positively reviewed.
After that, no more patches adding new features, only bugfixes. So I
guess there might be one additional beta (beta15), and then release
candidates. The new notebook will no
On Feb 26, 2012 9:13 PM, "Dan Drake" wrote:
>
> On Sun, 26 Feb 2012 at 11:24PM -0500, Jonathan Hanke wrote:
> > I am trying to build the latest development version of SAGE on a large
> > multiprocessor dell linux machine, and it failed with the following
> > error message. The error message is rat
On Sun, 26 Feb 2012 at 11:24PM -0500, Jonathan Hanke wrote:
> I am trying to build the latest development version of SAGE on a large
> multiprocessor dell linux machine, and it failed with the following
> error message. The error message is rather cryptic, so please let me
> know if there is any sp
Hi,
I am trying to build the latest development version of SAGE on a large
multiprocessor dell linux machine, and it failed with the following error
message. The error message is rather cryptic, so please let me know if
there is any specific architecture/log information you need. Thanks,
-Jon
Hi,
there are still a few failing tests.
Of course, there are the various gamma-related numerical problems, but
there is hope : http://trac.sagemath.org/sage_trac/ticket/12449
The vertex separation bug is still there even though a fix is almost
ready: http://trac.sagemath.org/sage_trac/ticket/12
On Feb 21, 2012, at 16:57 , R. Andrew Ohana wrote:
> On Tue, Feb 21, 2012 at 15:37, Justin C. Walker wrote:
>>
>> On Feb 21, 2012, at 14:16 , R. Andrew Ohana wrote:
>>
>>> On Tue, Feb 21, 2012 at 10:30, Justin C. Walker wrote:
On Feb 21, 2012, at 08:13 , R. Andrew Ohana wrote:
>> [
On Tue, Feb 21, 2012 at 15:37, Justin C. Walker wrote:
>
> On Feb 21, 2012, at 14:16 , R. Andrew Ohana wrote:
>
>> On Tue, Feb 21, 2012 at 10:30, Justin C. Walker wrote:
>>>
>>> On Feb 21, 2012, at 08:13 , R. Andrew Ohana wrote:
> [snip]
FYI, sqrt5 has been down for awhile since it is extrem
On Feb 21, 2012, at 14:16 , R. Andrew Ohana wrote:
> On Tue, Feb 21, 2012 at 10:30, Justin C. Walker wrote:
>>
>> On Feb 21, 2012, at 08:13 , R. Andrew Ohana wrote:
[snip]
>>> FYI, sqrt5 has been down for awhile since it is extremely prone to
>>> kernel panics and I have yet to figure out the i
On Tue, Feb 21, 2012 at 10:30, Justin C. Walker wrote:
>
> On Feb 21, 2012, at 08:13 , R. Andrew Ohana wrote:
>
>> On Tue, Feb 21, 2012 at 07:08, Dima Pasechnik wrote:
>>> In gmane.comp.mathematics.sage.devel, you wrote:
On Mon, Feb 20, 2012 at 4:28 AM, Dima Pasechnik wrote:
> Can we ge
On Feb 21, 2012, at 08:13 , R. Andrew Ohana wrote:
> On Tue, Feb 21, 2012 at 07:08, Dima Pasechnik wrote:
>> In gmane.comp.mathematics.sage.devel, you wrote:
>>> On Mon, Feb 20, 2012 at 4:28 AM, Dima Pasechnik wrote:
Can we get Lion on bsd.math.washington.edu ?
>>>
>>> I could, but then w
Don't forget:
* Upgrade to Python-2.7 (#9958)
which is already done, mostly thanks to François Bissey.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this gr
Hi Sage-Devel,
As decided on November 3, 2011, the blocker goals for sage-5.0 are:
1. Trac 12024: 90% doctest coverage:
http://trac.sagemath.org/sage_trac/ticket/12024
Status:
"sage-5.0.beta3-sage.math.washington.edu-x86_64-Linux$ ./sage -coverageall
Overall weighted coverage score: 86.5%
To
Hi,
A major blocker for Sage-5.0 is supporting OS X (version 10.7 -- the
version that has been out for months now).
Fortunately, it is now "relatively easy" to build sage-5.0.beta1 on OS
X 10.7 with XCode 4.x, and have it start up.
(1) Build [1] as usual.
(2) Apply Simon's patch trac11900_fix_si
Hi,
I made a test sage-5.0.prealpha0 image for Intel x64 system. It owns
the following functions:
a) Sage-5-prealaph0
b) Imagemagick-6.7.2
c) matplotlib-gui enabled (with _tkagg backend)
e) ffmpeg-0.8.4
f) firefox nightly build 12a1
g) jre-1.6u29
based on slackware live linux, porteus with Linux
On Wed, Jul 14, 2010 at 2:48 AM, David Kirkby wrote:
> On 14 July 2010 00:49, William Stein wrote:
>> Hi Sage Developers,
>>
>> I'm setting the Sage-5.0 target date for August 31, 2010 (see
>> http://trac.sagemath.org/sage_trac/milestone/sage-5.0). The goals
>> are:
>>
>> 1. Windows port via Cy
On 14 July 2010 00:49, William Stein wrote:
> Hi Sage Developers,
>
> I'm setting the Sage-5.0 target date for August 31, 2010 (see
> http://trac.sagemath.org/sage_trac/milestone/sage-5.0). The goals
> are:
>
> 1. Windows port via Cygwin:
> http://trac.sagemath.org/sage_trac/wiki/CygwinPort
>
Hi Sage Developers,
I'm setting the Sage-5.0 target date for August 31, 2010 (see
http://trac.sagemath.org/sage_trac/milestone/sage-5.0). The goals
are:
1. Windows port via Cygwin: http://trac.sagemath.org/sage_trac/wiki/CygwinPort
2. Upgrade PARI to svn: #9343
3. Upgrade MPIR to version 2.x:
58 matches
Mail list logo
