On Nov 7, 6:45 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Nov 5, 2008, at 15:44 , mabshoff wrote:
> Mac OS X, 10.4.11 (Core 2 Duo):
> Built w/o problems
> All tests passed
>
> Mac OS X, 10.5.5 (Dual Quad Xeon):
> Built w/o problems. Testing ("make -j2 test") gave 1 failu
OK, that's now #4463.
On Nov 7, 8:21 am, mabshoff <[EMAIL PROTECTED]> wrote:
> On Nov 7, 6:13 am, mhampton <[EMAIL PROTECTED]> wrote:
>
> > I just had one timeout failure on a PPC mac running 10.4, on modular/
> > abvar/homspace.py, plus the following malloc error which didn't cause
> > the test
On Nov 5, 2008, at 15:44 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
> fixed all numerical doctest noise from #788 (I even reverted a small
> number of changes) and otherwise merged a couple other nice patches.
>
> If this release buil
On Nov 7, 6:13 am, mhampton <[EMAIL PROTECTED]> wrote:
> I just had one timeout failure on a PPC mac running 10.4, on modular/
> abvar/homspace.py, plus the following malloc error which didn't cause
> the test to fail but maybe its worth noting:
>
> sage -t devel/sage/sage/libs/pari/gen.pyx
> p
I just had one timeout failure on a PPC mac running 10.4, on modular/
abvar/homspace.py, plus the following malloc error which didn't cause
the test to fail but maybe its worth noting:
sage -t devel/sage/sage/libs/pari/gen.pyx
python(5728) malloc: *** vm_allocate(size=409600) failed (error
c
All tests passed on my intel mac, running 10.4. I am building and
testing on a PPC 10.4 as well, but I won't be awake when that
finishes.
-Marshall
On Nov 6, 9:41 pm, Dan Drake <[EMAIL PROTECTED]> wrote:
> On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
> > [EMAIL PROTECTED]:~/sagefil
On Thu, 06 Nov 2008 at 01:09PM -0500, David Joyner wrote:
> [EMAIL PROTECTED]:~/sagefiles/sage-3.2.alpha3$ ./sage -t
> devel/sage/sage/interfaces/lisp.py
> sage -t devel/sage/sage/interfaces/lisp.py
> [11.8 s]
I'm using Intrepid amd64 and get the same failures as Franco.
> [EMAIL PROTEC
mabshoff wrote:
> Jaap,
>
> can you please open a ticket for that one. I suspect that we don't
> have anything tested via long or that the tests aren't properly marked
> "#long time". This one has popped up so often that we really ought to
> fix it once and for all since you hit it every time.
>
On Nov 6, 1:28 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 1:27 PM, mabshoff <[EMAIL PROTECTED]> wrote:
> > Yeah, that would be great. I am curious if we should push for an rc0
> > fixing only critical bugs in the next 24 hours to release shortly or
> > if we shoul
On Thu, Nov 6, 2008 at 1:27 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Nov 6, 1:24 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
>
>
>> > Did you run the tests on the build farm or is
>> > there coming more?
>>
>> I only built on bsd and sage.math and modular. I haven't
>> built on th
On Nov 6, 1:24 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Did you run the tests on the build farm or is
> > there coming more?
>
> I only built on bsd and sage.math and modular. I haven't
> built on the build farm. Should I?
Yeah, that would be great. I am curious if we should push
On Thu, Nov 6, 2008 at 1:21 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Nov 6, 6:11 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Wed, Nov 5, 2008 at 3:44 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>>
>> > Hello folks,
>>
>> > here goes 3.2.alpha3 - somewhat later than planned. Hopeful
On Nov 6, 8:22 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
> > As usual sources and a sage.math binary is in
>
> >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
>
> On Fedora 9, 32 bits:
> --
> The following
On Nov 6, 6:11 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 5, 2008 at 3:44 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
>
> > here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
> > fixed all numerical doctest noise from #788 (I even reverted a small
On Nov 6, 12:42 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/11/6 John Cremona <[EMAIL PROTECTED]>:
>
> > Whatever caused that I don't know, but I started again from a fresh
> > download and all was fine. Sorry for the noise.
>
> -testall -long: all passed
Hi John,
I would have guess
2008/11/6 John Cremona <[EMAIL PROTECTED]>:
> Whatever caused that I don't know, but I started again from a fresh
> download and all was fine. Sorry for the noise.
-testall -long: all passed
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@go
On Thu, Nov 6, 2008 at 11:03 AM, Franco Saliola <[EMAIL PROTECTED]> wrote:
> Thanks for checking. I am mystified too.
>
> Other than a few hangs during testall, all tests besides lisp.py
> passed. Which was unexpected because I thought other code that relies
> on lisp.py would fail as well.
That'
Hi David, hi Franco,
currently Sage has a known weakness with the Maxima synchronization
resp. the lisp processes that are started by Maxima, which hits only
sporadically and seems to be related to dynamical memory allocation
done deep in the bowels of the lisp implementation.
It has never been
On Thu, Nov 6, 2008 at 7:09 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Thu, Nov 6, 2008 at 12:52 PM, Franco Saliola <[EMAIL PROTECTED]> wrote:
>>
>> Hello David,
>>
>> On Thu, Nov 6, 2008 at 1:51 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>>
>>> With amd64 intrepid ibex, it builds fine bu
On Thu, Nov 6, 2008 at 12:52 PM, Franco Saliola <[EMAIL PROTECTED]> wrote:
>
> Hello David,
>
> On Thu, Nov 6, 2008 at 1:51 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
>> With amd64 intrepid ibex, it builds fine but sage -testall
>> seems to have the same locking-up issues as with the alpha2 ver
Hello David,
On Thu, Nov 6, 2008 at 1:51 PM, David Joyner <[EMAIL PROTECTED]> wrote:
> With amd64 intrepid ibex, it builds fine but sage -testall
> seems to have the same locking-up issues as with the alpha2 version.
I'm too am using amd64 intrepid ibex and having the same issues.
The followin
Whatever caused that I don't know, but I started again from a fresh
download and all was fine. Sorry for the noise.
2008/11/6 John Cremona <[EMAIL PROTECTED]>:
> On my laptop which normally builds Sage fine I get this (at the end of
> install.log):
>
> sage-3.2.alpha3/.hg/store/data/sagebuild.py
mabshoff wrote:
> Hello folks,
>
> here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
> fixed all numerical doctest noise from #788 (I even reverted a small
> number of changes) and otherwise merged a couple other nice patches.
>
> If this release builds and doctests fine it will
Build ok and all tests pass on here (32-bit linux):
Linux version 2.6.16.60-0.31-smp ([EMAIL PROTECTED]) (gcc version 4.1.2
20070115 (SUSE Linux)) #1 SMP Tue Oct 7 16:16:29 UTC 2008
and here (64-bit linux):
Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3
(Ubuntu 4.2.3-2ub
On Debian stable 32-bit one test fails:
sage -t devel/sage/sage/interfaces/r.py
**
File "/local/data/huss/software/sage-3.2.alpha3/tmp/r.py", line 549:
sage: r.library('foobar')
Expected:
Traceback (most recent call last
Hi,
on Core2 Duo Intel OS X 10.4.11 (Xcdoe 2.5) Sage.3.2.alpha3 builds
fine.
I immediately ran "MAKE testlong", and it only gives the two long
known
failures (trac tickets in the 3xxx range):
--
The following tests failed:
On Wed, Nov 5, 2008 at 3:44 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> here goes 3.2.alpha3 - somewhat later than planned. Hopefully we
> fixed all numerical doctest noise from #788 (I even reverted a small
> number of changes) and otherwise merged a couple other nice patches.
On Thu, Nov 6, 2008 at 7:51 AM, David Joyner <[EMAIL PROTECTED]> wrote:
> With amd64 intrepid ibex, it builds fine but sage -testall
> seems to have the same locking-up issues as with the alpha2 version.
> I can ctrl c to get out of the doc files, and it will pass on to testing
> the next one, but
On my laptop which normally builds Sage fine I get this (at the end of
install.log):
sage-3.2.alpha3/.hg/store/data/sagebuild.py.i
sage-3.2.alpha3/.hg/store/data/setup.py.d
sage-3.2.alpha3/.hg/store/data/setup.py.i
sage-3.2.alpha3/.hg/store/data/setupnb.py.i
sage-3.2.alpha3/.hg/store/data/spkg-de
With amd64 intrepid ibex, it builds fine but sage -testall
seems to have the same locking-up issues as with the alpha2 version.
I can ctrl c to get out of the doc files, and it will pass on to testing
the next one, but when I ctrl-c at
sage -t devel/sage/sage/libs/fplll/fplll.pyx
it kicks me out
30 matches
Mail list logo
