On Sep 23, 4:05 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> > wrote:
>
> > > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> >
>
> > > I'll
On Sep 23, 4:05 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> > wrote:
>
> > > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> >
>
> > > I'll open
Hi,
On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> wrote:
>
> > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'll open more tickets for other failures, as soon I can say for sure
> > "it' only timing"
On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
> I'll open more tickets for other failures, as soon I can say for sure
> "it' only timing" and have a new "good" timing constant.
Please do not open any more ticket
On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/9/23 William Stein <[EMAIL PROTECTED]>:
>
> I still don't know if this is going to help the MACOS problem with my
> sll_finite_field odctest though!
>
> John
>
Hi all,
first some on-topic data:
on my PPC PowerBook with Mac OS
2008/9/23 William Stein <[EMAIL PROTECTED]>:
>
> On Mon, Sep 22, 2008 at 6:11 PM, Craig Citro <[EMAIL PROTECTED]> wrote:
>>
>> Hi John,
>>
>>> That is not in itself slow:
>>> sage: time pp=pari.primes_up_to_n(10^8)
>>> CPU times: user 0.69 s, sys: 0.30 s, total: 1.00 s
>>> Wall time: 1.00 s
>>>
>>
On Mon, Sep 22, 2008 at 6:11 PM, Craig Citro <[EMAIL PROTECTED]> wrote:
>
> Hi John,
>
>> That is not in itself slow:
>> sage: time pp=pari.primes_up_to_n(10^8)
>> CPU times: user 0.69 s, sys: 0.30 s, total: 1.00 s
>> Wall time: 1.00 s
>>
>> However note that
>>
>> sage: time pp=prime_range(10^8)
Hi John,
> That is not in itself slow:
> sage: time pp=pari.primes_up_to_n(10^8)
> CPU times: user 0.69 s, sys: 0.30 s, total: 1.00 s
> Wall time: 1.00 s
>
> However note that
>
> sage: time pp=prime_range(10^8)
> CPU times: user 143.74 s, sys: 1.51 s, total: 145.26 s
> Wall time: 145.93 s
>
> wi
2008/9/22 Georg S. Weber <[EMAIL PROTECTED]>:
>
>
>
> On 22 Sep., 22:17, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> 2008/9/22 Georg S. Weber <[EMAIL PROTECTED]>:
>>
>>
>>
>>
>>
>> > On 22 Sep., 10:39, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> >> 2008/9/21 Georg S. Weber <[EMAIL PROTECTED]>:
>
On 22 Sep., 22:17, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/9/22 Georg S. Weber <[EMAIL PROTECTED]>:
>
>
>
>
>
> > On 22 Sep., 10:39, "John Cremona" <[EMAIL PROTECTED]> wrote:
> >> 2008/9/21 Georg S. Weber <[EMAIL PROTECTED]>:
>
> >> > Hi John,
>
> >> > On 21 Sep., 21:16, "John Cremona"
2008/9/22 Georg S. Weber <[EMAIL PROTECTED]>:
>
>
>
> On 22 Sep., 10:39, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> 2008/9/21 Georg S. Weber <[EMAIL PROTECTED]>:
>>
>>
>>
>>
>>
>> > Hi John,
>>
>> > On 21 Sep., 21:16, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> >> The long test in ell_finite_fi
On 22 Sep., 10:39, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/9/21 Georg S. Weber <[EMAIL PROTECTED]>:
>
>
>
>
>
> > Hi John,
>
> > On 21 Sep., 21:16, "John Cremona" <[EMAIL PROTECTED]> wrote:
> >> The long test in ell_finite_field.py which causes problems on this
> >> platform is this:
>
2008/9/21 Georg S. Weber <[EMAIL PROTECTED]>:
>
> Hi John,
>
> On 21 Sep., 21:16, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> The long test in ell_finite_field.py which causes problems on this
>> platform is this:
>> sage: E = EllipticCurve('389a')
>> sage: for p in prime
Hi John,
On 21 Sep., 21:16, "John Cremona" <[EMAIL PROTECTED]> wrote:
> The long test in ell_finite_field.py which causes problems on this
> platform is this:
> sage: E = EllipticCurve('389a')
> sage: for p in prime_range(1): #long time (~20s)
>
On Sun, Sep 21, 2008 at 12:04 PM, Georg S. Weber
<[EMAIL PROTECTED]> wrote:
>
> On Intel MacBook OS X 10.4 / Xcode 2.5 (yes, I upgraded), nothing
> really new for 3.1.3.alpha0:
>
> builds fine
>
> make test choked on two of three runs on /modular/abvar/homspace.py,
> and passed on the third
>
> ma
The long test in ell_finite_field.py which causes problems on this
platform is this:
sage: E = EllipticCurve('389a')
sage: for p in prime_range(1): #long time (~20s)
... if p != 389:
... G=E.change_ring(GF(p)).abelian_g
On Intel MacBook OS X 10.4 / Xcode 2.5 (yes, I upgraded), nothing
really new for 3.1.3.alpha0:
builds fine
make test choked on two of three runs on /modular/abvar/homspace.py,
and passed on the third
make testlong choked on sr.py and ell_finite_field.py (the known ones
from the 3.1.2 cycle)
T
mabshoff wrote:
> Avast, me hearties
>
> since it is International Talk Like A Pirate Day, but don't worry
> about that. 3.1.3.alpha0 is out and this time we are shooting for a
> quicker release cycle. Various patches and spkgs got merged and we are
> off to a good start to 3.1.3 I hope. Souces a
>
>> > In general I will hopefully fix this issue (i.e. restart the build on
>> > failure a couple times) in 3.1.3.
>>
>> That did not work for me before... Anyway it's possible there are
>> other problems with Warwick computers this weekend since now Bill's
>> machine id not answering my call ei
On Sep 20, 1:48 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/9/20 mabshoff <[EMAIL PROTECTED]>:
> >> which is plain silly since the machine has 4 dual core processors and
> >> *nothing* else is running on it.
>
> > The kernel on that box probably has throttling enabled which increase
2008/9/20 mabshoff <[EMAIL PROTECTED]>:
>
> On Sep 20, 5:54 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> Hi John,
>
>> Since the usual 64-bit machine I test on (thanks, Samir) is offline
>> today I used a similar one (thanks, Bill!) knowing that its owner --
>> Bill "Fllint" Hart -- is safely
On Sep 20, 5:54 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> Since the usual 64-bit machine I test on (thanks, Samir) is offline
> today I used a similar one (thanks, Bill!) knowing that its owner --
> Bill "Fllint" Hart -- is safely in the southern hemisphere.
>
> And then I remembe
A on ye amd64 hardy heron, build and sage -testall went smart and true!
On Fri, Sep 19, 2008 at 11:28 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Avast, me hearties
>
> since it is International Talk Like A Pirate Day, but don't worry
> about that. 3.1.3.alpha0 is out and this time we ar
Dear William,
On Sep 20, 5:47 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> You probably didn't properly merge hg_scripts or something. Try
>
> sage: hg_scripts.merge()
I don't know how I managed to not properly merge hg_scripts.
But the banner is now updated.
Thank you!
Simon
--~--~--
On Sat, Sep 20, 2008 at 8:38 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear William
>
> On Sep 20, 5:23 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Sat, Sep 20, 2008 at 6:42 AM, Simon King <[EMAIL PROTECTED]> wrote:
>> > Will a bottle o' rum help, or what else?
>>
>> This looks like a
Dear William
On Sep 20, 5:23 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 20, 2008 at 6:42 AM, Simon King <[EMAIL PROTECTED]> wrote:
> > Will a bottle o' rum help, or what else?
>
> This looks like a corrupted download. Can you delete clisp stuff from
> spkg/standard and try agai
2008/9/20 John Cremona <[EMAIL PROTECTED]>:
> Since the usual 64-bit machine I test on (thanks, Samir) is offline
> today I used a similar one (thanks, Bill!) knowing that its owner --
> Bill "Fllint" Hart -- is safely in the southern hemisphere.
>
> And then I remembered that on that machine Sage
On Sat, Sep 20, 2008 at 6:42 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> On Sep 20, 5:40 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> Arrr, the bra'e among you can type "sage -upgrade" t' upgrade t' sage-3.1.2.
>>
>> Aye. William
>
> "Coward lisp" (clisp) didn't show up:
> ...
> clisp-2.46
On Sep 20, 5:40 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Arrr, the bra'e among you can type "sage -upgrade" t' upgrade t' sage-3.1.2.
>
> Aye. William
"Coward lisp" (clisp) didn't show up:
...
clisp-2.46.p7/src/src/clos-genfun2a.lisp
Finished extraction
There is no spkg-install script, n
Since the usual 64-bit machine I test on (thanks, Samir) is offline
today I used a similar one (thanks, Bill!) knowing that its owner --
Bill "Fllint" Hart -- is safely in the southern hemisphere.
And then I remembered that on that machine Sage won't build because of this:
ATLAS failed to build b
On Fri, Sep 19, 2008 at 8:28 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Avast, me hearties
>
> since it is International Talk Like A Pirate Day, but don't worry
> about that.
Ahoy,
Arrr, the bra'e among you can type "sage -upgrade" t' upgrade t' sage-3.1.2.
Aye. William
>3.1.3.alpha0 is out
31 matches
Mail list logo
