On Fri, Feb 6, 2009 at 9:42 AM, mabshoff wrote:
>
>
>
> On Feb 6, 6:38 am, David Joyner wrote:
>> Sorry for the late reply: on ubuntu amd64 hardy heron, only 1 failure,
>> very similar
>> to one already reported by William:
>
> Hi David,
>
> can you see if the patch at #5172 fixes it for you? It
On Feb 6, 6:38 am, David Joyner wrote:
> Sorry for the late reply: on ubuntu amd64 hardy heron, only 1 failure,
> very similar
> to one already reported by William:
Hi David,
can you see if the patch at #5172 fixes it for you? It has already
been merged in alpha6, but in case there is still a
Sorry for the late reply: on ubuntu amd64 hardy heron, only 1 failure,
very similar
to one already reported by William:
w...@tinah:~/sagefiles/sage-3.3.alpha5$ ./sage -t
"devel/sage/sage/calculus/calculus.py"
sage -t "devel/sage/sage/calculus/calculus.py"
***
mabshoff wrote:
>
>
> On Feb 5, 12:28 pm, Jaap Spies wrote:
>> mabshoff wrote:
>>> something deeper inside libSingular. I have posted some speculation
>>> why some runs fail and other runs do not, so I am not going to repeat
>>> it here and bore 99.5% of Sage devs to death again :)
>> I'm one o
On Feb 5, 1:09 pm, William Stein wrote:
> On Thu, Feb 5, 2009 at 12:28 PM, Jaap Spies wrote:
>
> OS X PowerPC 10.5:
>
> sage -t -long "devel/sage/sage/rings/polynomial/toy_d_basis.py"
Got a fix that will be merged in a minute.
> sage -t -long
> "devel/sage/sage/schemes/ell
Oops, I missed some.
> opteron Ubuntu 6.10 (sagemath.org): 1 failure
>
> sage -t -long "devel/sage/sage/calculus/calculus.py"
> Total time for all tests: 5690.1 seconds
>
> NOISE:
> sage -t -long "devel/sage/sage/calculus/calculus.py"
> *
On Feb 5, 12:28 pm, Jaap Spies wrote:
> mabshoff wrote:
> > something deeper inside libSingular. I have posted some speculation
> > why some runs fail and other runs do not, so I am not going to repeat
> > it here and bore 99.5% of Sage devs to death again :)
>
> I'm one of the other 0.5%! This
On Thu, Feb 5, 2009 at 12:28 PM, Jaap Spies wrote:
>
> mabshoff wrote:
>
>> something deeper inside libSingular. I have posted some speculation
>> why some runs fail and other runs do not, so I am not going to repeat
>> it here and bore 99.5% of Sage devs to death again :)
>>
>
> I'm one of the o
mabshoff wrote:
> something deeper inside libSingular. I have posted some speculation
> why some runs fail and other runs do not, so I am not going to repeat
> it here and bore 99.5% of Sage devs to death again :)
>
I'm one of the other 0.5%! This will not stop me :)
I have news from my Fedora
On Feb 4, 1:16 pm, John H Palmieri wrote:
> On Feb 4, 6:26 am, mabshoff wrote:
>
> > Hello folks,
>
> > 3.3.alpha5 is out and unlike 3.3.alpha4 it is being announced on sage-
> > devel.
>
> [snip]
>
> > If you want to get a patch in before the
> > ReST transition now is the time to get it revi
On Feb 4, 6:26 am, mabshoff wrote:
> Hello folks,
>
> 3.3.alpha5 is out and unlike 3.3.alpha4 it is being announced on sage-
> devel.
[snip]
> If you want to get a patch in before the
> ReST transition now is the time to get it reviewed and merged since
> the window is closing rapidly, i.e. exp
On Feb 4, 12:41 pm, Jaap Spies wrote:
> mabshoff wrote:
> Hi Michael,
Hi Jaap,
> > So far the issue seems to be only at startup, i.e once Sage is up and
> > running I have not observed a libSingular related memory failure. And
> > the fix so far is only a hunch, I have not tested it. The a
mabshoff wrote:
>
>
> On Feb 4, 10:24 am, William Stein wrote:
>> On Wed, Feb 4, 2009 at 10:01 AM, Jaap Spies wrote:
>
>
>
>>> On Fedora 9, 32 bits I had those known issues
>>> plus 11 mysterious memory errors.
>> If we can't fix this fedora bug before the release, we *have* to put a
>> run
On Feb 4, 10:24 am, William Stein wrote:
> On Wed, Feb 4, 2009 at 10:01 AM, Jaap Spies wrote:
> > On Fedora 9, 32 bits I had those known issues
> > plus 11 mysterious memory errors.
>
> If we can't fix this fedora bug before the release, we *have* to put a
> runtime check to see if Sage is
On Wed, Feb 4, 2009 at 10:01 AM, Jaap Spies wrote:
>
> mabshoff wrote:
>> Hello folks,
>>
>> 3.3.alpha5 is out and unlike 3.3.alpha4 it is being announced on sage-
>> devel. The main problem with alpha4 as you might have seen already was
>> that I broke the NTL dylib build while removing some cod
mabshoff wrote:
> Hello folks,
>
> 3.3.alpha5 is out and unlike 3.3.alpha4 it is being announced on sage-
> devel. The main problem with alpha4 as you might have seen already was
> that I broke the NTL dylib build while removing some code from sage-
> env. Since then I also merged a bunch of othe
16 matches
Mail list logo
