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.
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
16 matches
Mail list logo