On May 4, 5:11 am, elflapper <[EMAIL PROTECTED]> wrote:
> 512 mb
> I think these are relevant part I forgot to post.
> Exception exceptions.TypeError: TypeError(RuntimeError('Unable to
> start maxima b
> ecause the command \'maxima -p "/mnt/documents/sage-3.0.1.rc0/local/
> bin/sage-max
> ima
512 mb
I think these are relevant part I forgot to post.
--copy and paste---
sage -t devel/sage/sage/rings/polynomial/pbori.pyx
**
File "/mnt/documents/sage-3.0.1.rc0/tmp/pbori.py", line 2512:
sage: f(x=var('a'),y=va
On Sat, May 3, 2008 at 7:53 PM, elflapper <[EMAIL PROTECTED]> wrote:
>
> I just ran the test:
> The following tests failed:
>
>
> sage -t devel/sage/sage/rings/polynomial/pbori.pyx
> sage -t devel/sage/sage/rings/complex_double.pyx
> Total time for all tests: 5126.3 seconds
>
I just ran the test:
The following tests failed:
sage -t devel/sage/sage/rings/polynomial/pbori.pyx
sage -t devel/sage/sage/rings/complex_double.pyx
Total time for all tests: 5126.3 seconds
On Archlinux x86
On May 3, 12:17 am, elflapper <[EMAIL PROTECTED]> wrote:
> This build
On Sat, May 3, 2008 at 1:24 PM, Willem Jan Palenstijn <[EMAIL PROTECTED]> wrote:
>
> On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote:
> > On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx
>
> > know issue. Track ticket s
On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote:
> On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx
> know issue. Track ticket should be up shortly. Singular related.
This is now #3098.
It is caused by a rather subtle prob
On Sat, May 3, 2008 at 11:57 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Build testing of sage-3.0.1.rc0:
>
> Hi,
>
>
> > Powerpc OS X 10.5:
> > sage -t devel/sage/sage/dsage/tests/testdoc.py
> > sage -t deve
On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Build testing of sage-3.0.1.rc0:
Hi,
> Powerpc OS X 10.5:
> sage -t devel/sage/sage/dsage/tests/testdoc.py
> sage -t devel/sage/sage/modular/abvar/abvar.py
> sage -t devel/sage/sage/modular/abvar/homspace.
Build testing of sage-3.0.1.rc0:
Powerpc OS X 10.5:
sage -t devel/sage/sage/dsage/tests/testdoc.py
sage -t devel/sage/sage/modular/abvar/abvar.py
sage -t devel/sage/sage/modular/abvar/homspace.py
sage -t devel/sage/sage/server/simple/twist.py
Total time for all
On May 3, 4:18 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote:
> Built fine on
Hi Alex,
> Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007
> i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux
>
> Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to k
On May 3, 7:37 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hi David,
> Sorry. Here it ishttp://sage.math.washington.edu/home/wdj/patches/install.log
> (or will be in a few minutes - it's still uploading).
I think I found it: The working version of mwrank.so is compiled with g
++, while the no
Built fine on
Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007
i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux
Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to kill
it. I've put the build log at
http://bayes.colby.edu/~ghitza/inst
On Sat, May 3, 2008 at 1:19 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi David,
>
>
> > > Can you post a link to the build log? This is very li
On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
Hi David,
> > Can you post a link to the build log? This is very likely related to
> > pbuild's different linker flags. We should be able to hunt this down
>
On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>
> > Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
> > rather old machine
> > though, so many this is not something to wor
On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hi David,
> Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
> rather old machine
> though, so many this is not something to worry about.)
Yes, it is ;)
> export SAGE_PBUILD=yes
> export SAGE_BUILD_THREADS=2
> make
>
Possibly strange results on an ubuntu 7.10amd64 machine. (It is a
rather old machine
though, so many this is not something to worry about.)
export SAGE_PBUILD=yes
export SAGE_BUILD_THREADS=2
make
Build went fine. However, sage -testall started messing up almost immediately.
Here is some of it:
On May 3, 5:26 pm, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Andrzej,
> built and tested on Arch 32, only one failure (were 3 for alpha)...
> same as with 3.0.0:
>
> sage -t 3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx
> **
Hi,
built and tested on Arch 32, only one failure (were 3 for alpha)...
same as with 3.0.0:
sage -t 3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx
**
File "/opt/sage/tmp/complex_double.py", line 1659:
sage: z^2 - z + 1
On May 3, 4:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> ok , I thought I should have been listening in on IRC when sage-devel
> went quiet!
Yes, #sage-devel is often the place to get quick answers, especially
to debug problems.
> This doesn't actually tell me what I should do.
ok , I thought I should have been listening in on IRC when sage-devel
went quiet!
This doesn't actually tell me what I should do. (You were right that
this is with PBUILD, by the way). But I killed the --testall.
Any ideas on the 8 rogue sage processes I have goung back to April 10?
In full t
On May 3, 3:07 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
> seems to have stalled doing testall at this point:
>
> sage -t devel/sage/sage/dsage/dist_functions/all.py
> [1.3 s]
> sage -t devel/sage/sage/dsage/sc
All ok on my 32-bit machine:
All tests passed!
Total time for all tests: 4034.3 seconds
Please see /home/jec/sage-3.0.1.rc0/tmp/test.log for the complete log
from this test.
[EMAIL PROTECTED] -a
Linux fermat 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008
i686 GNU/Linux
2008/5/3 John Crem
All tests passed on my intel mac pro, running OS X 10.4.11.
-M. Hampton
On May 3, 8:07 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
> seems to have stalled doing testall at this point:
>
> sage -t devel/sage/sage/dsage/dist
Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one
seems to have stalled doing testall at this point:
sage -t devel/sage/sage/dsage/dist_functions/all.py
[1.3 s]
sage -t devel/sage/sage/dsage/scripts/nodoctest.py (skipping) --
nodoctest.py file in directory
sage -t d
This builds without error on Archlinux (3.0 didn't build with just
'make')!!!
On May 2, 11:43 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This is the end of the 3.0.1 release cycle. The build was announced
> in IRC about eight hours ago, but since I took a long nap in the
> meantime I
26 matches
Mail list logo
