On Dec 20, 12:45 pm, Robert Bradshaw
wrote:
> On Dec 20, 2008, at 12:31 PM, Craig Citro wrote:
>
> > That example was with CyclotomicField(12) and CyclotomicField(132) ...
>
> Ah. I bet the time was spent resolving the roots of CyclotomicField
> (132) to high enough precision to distinguish the
On Dec 20, 2008, at 12:31 PM, Craig Citro wrote:
> That example was with CyclotomicField(12) and CyclotomicField(132) ...
Ah. I bet the time was spent resolving the roots of CyclotomicField
(132) to high enough precision to distinguish them. If you don't come
up with a patch for this, I'll (p
On Dec 20, 12:31 pm, "Craig Citro" wrote:
Hi,
> That example was with CyclotomicField(12) and CyclotomicField(132) ...
>
> -cc
Please open a ticket against 3.3, but I think the patch (should it
exist by then [working with reverse psychology here :)]) will only go
in after 3.3.alpha0, i.e. when
That example was with CyclotomicField(12) and CyclotomicField(132) ...
-cc
On Sat, Dec 20, 2008 at 12:25 PM, Robert Bradshaw
wrote:
>
> On Dec 20, 2008, at 12:16 PM, mabshoff wrote:
>
>> On Dec 20, 12:11 pm, "Craig Citro" wrote:
>>
>>
>>
>>
>>> So just running this through prun suggests that
On Dec 20, 2008, at 12:16 PM, mabshoff wrote:
> On Dec 20, 12:11 pm, "Craig Citro" wrote:
>
>
>
>
>> So just running this through prun suggests that it's something
>> related
>> to coercion:
>>
>>ncalls tottime percall cumtime percall filename:lineno
>> (function)
>> 17/11 13.8
On Dec 20, 12:11 pm, "Craig Citro" wrote:
> So just running this through prun suggests that it's something related
> to coercion:
>
> ncalls tottime percall cumtime percall filename:lineno(function)
> 17/11 13.884 0.817 14.137 1.285
> number_field.py:1502(_coerce_map_fr
> Using --verbose, first, this doctest takes a *long* time (minutes):
>
>z, n =
> sage.modular.modform.eisenstein_submodule.cyclotomic_restriction(L,N)###line
> 401:_sage_>>> z, n =
> sage.modular.modform.eisenstein_submodule.cyclotomic_restriction(L,N)
> Expecting nothing
>
So just runn
On Dec 20, 10:21 am, "William Stein" wrote:
> On Fri, Dec 19, 2008 at 4:07 PM, Craig Citro wrote:
Hi,
> When I just built some of the binaries for sage-3.2.2 I had this file
> (eisenstein_submodule.py) timeout on two of my build machines after
> 360 seconds. One is the G5 in Clement's of
On Fri, Dec 19, 2008 at 4:07 PM, Craig Citro wrote:
>
>> eisenstein_submodule, sorry I wasn't more specific.
>>
>
> Hmm, interesting. Do you have the log? I'm just surprised that
> anything could cause that file to timeout, especially without causing
> anything else to timeout. Could I con you in
I reran it and all tests passed in 54 seconds. This is after
rebuilding sage to make sure all the cython stuff was in the right
place. The machine has a 1.5 Ghz powerpc G4 with 512 MB of RAM.
-Marshall
On Dec 19, 6:07 pm, "Craig Citro" wrote:
> > eisenstein_submodule, sorry I wasn't more spec
> eisenstein_submodule, sorry I wasn't more specific.
>
Hmm, interesting. Do you have the log? I'm just surprised that
anything could cause that file to timeout, especially without causing
anything else to timeout. Could I con you into running that test
again, and seeing if it still times out? If
eisenstein_submodule, sorry I wasn't more specific.
-Marshall
On Dec 19, 1:00 pm, "Craig Citro" wrote:
> > My ppc powerbook is still slaving away on tests, its almost done and
> > so far just has timeout failures on eisenstein and calculus.py.
>
> What file was the eisenstein timeout on?
>
> -c
> My ppc powerbook is still slaving away on tests, its almost done and
> so far just has timeout failures on eisenstein and calculus.py.
>
What file was the eisenstein timeout on?
-cc
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegro
On Dec 19, 8:53 am, mhampton wrote:
Hi Marshall,
> I reran the test and it passed. sage -maxima works fine. I did
> realize that I said something incorrect, it looks like the install I
> am using was originally from the 3.2.1.rc0 source, and I have upgraded
> and renamed it several times si
I reran the test and it passed. sage -maxima works fine. I did
realize that I said something incorrect, it looks like the install I
am using was originally from the 3.2.1.rc0 source, and I have upgraded
and renamed it several times since then. So it is not too weird an
event. Some of the c sou
On Dec 19, 5:21 am, mhampton wrote:
> I had an interesting failure on an intel mac running 10.5. Let me
> describe my setup a bit since I think its relevant: because of the new
> upgrade flexibility, I decided to have a "stable" sage and an
> "unstable" sage on my machine, and I delete almost
I had an interesting failure on an intel mac running 10.5. Let me
describe my setup a bit since I think its relevant: because of the new
upgrade flexibility, I decided to have a "stable" sage and an
"unstable" sage on my machine, and I delete almost all of my other
sage builds. I changed the sag
On Dec 18, 2008, at 23:03 , mabshoff wrote:
>
>
>
> On Dec 18, 11:00 pm, "Justin C. Walker" wrote:
>> Hi, Michael,
>
> Hi Justin,
>
>> I applied the 'doc' patch to the rc1 build, and it failed:
>>
>> applying /SandBox/DownLoads/trac_4828_doc.patch
>> unable to find 'commontex/patchlevel.tex' fo
On Dec 18, 11:00 pm, "Justin C. Walker" wrote:
> Hi, Michael,
Hi Justin,
> I applied the 'doc' patch to the rc1 build, and it failed:
>
> applying /SandBox/DownLoads/trac_4828_doc.patch
> unable to find 'commontex/patchlevel.tex' for patching
> 1 out of 1 hunk FAILED -- saving rejects to file
Hi, Michael,
On Dec 18, 2008, at 22:36 , mabshoff wrote:
> On Dec 18, 10:05 pm, John H Palmieri wrote:
>> On Dec 17, 10:20 am, mabshoff wrote:
[snip]
>> If I modify ranker.py to delete the accent, the error goes away.
>
> I thought that had been fixed by another patch, but apparently it
> didn'
On Dec 18, 10:05 pm, John H Palmieri wrote:
> On Dec 17, 10:20 am, mabshoff wrote:
>
Hi,
>
> > Please give this release a good beating and report any issues.
>
> On Intel Mac OS X 10.5, built fine from scratch, all tests passed.
> However, if I run 'sage -clone TEMP' and then run sage, I get
On Dec 17, 10:20 am, mabshoff wrote:
>
> Please give this release a good beating and report any issues.
On Intel Mac OS X 10.5, built fine from scratch, all tests passed.
However, if I run 'sage -clone TEMP' and then run sage, I get an error
from an accent in "Thiery":
SyntaxError: Non-ASCII ch
I get the same failure in multi_polynomial_ideal.py in 64-bit RHEL5
(and nothing else).
Kiran
On Dec 17, 4:43 pm, Jaap Spies wrote:
> mabshoff wrote:
> > On Dec 17, 1:27 pm, Jaap Spies wrote:
> >> Jaap Spies wrote:
>
> > Hi Jaap,
>
> >>>
On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very so
Same for me on 32-bit Suse.
On Dec 18, 8:54 am, "John Cremona" wrote:
> Built fine and all tests passed on: 32-bit ubuntu; 64-bit Suse.
>
> John
>
> 2008/12/18 Justin C. Walker :
>
>
>
> > On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> >> Hello folks,
>
> >> here goes 3.2.2.rc1. We finally mer
Built fine and all tests passed on: 32-bit ubuntu; 64-bit Suse.
John
2008/12/18 Justin C. Walker :
>
>
> On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
>>
>> Hello folks,
>>
>> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
>> that the last major piece of code is in 3.2.2.
On Dec 17, 2008, at 10:20 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very so
mabshoff wrote:
> On Dec 17, 1:27 pm, Jaap Spies wrote:
>> Jaap Spies wrote:
>
> Hi Jaap,
>
>>> --
>>> The following tests failed:
>>>sage -t pha2/devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py
>>> # 1 doctest
All tests passed on an intel mac, 10.4.11.
-M. Hampton
On Dec 17, 12:20 pm, mabshoff wrote:
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug c
Gary Furnish wrote:
> It should give the relative path to where you ran the test from... if
> its not, thats a bug.
>
I did ./sage -tp 2 devel/sage/sage
Jaap
> On Wed, Dec 17, 2008 at 2:31 PM, mabshoff wrote:
>> On Dec 17, 1:27 pm, Jaap Spies wrote:
>>> Jaap Spies wrote:
>> Hi Jaap,
>>
>>>
It should give the relative path to where you ran the test from... if
its not, thats a bug.
On Wed, Dec 17, 2008 at 2:31 PM, mabshoff wrote:
>
> On Dec 17, 1:27 pm, Jaap Spies wrote:
>> Jaap Spies wrote:
>
> Hi Jaap,
>
>> > --
On Dec 17, 1:27 pm, Jaap Spies wrote:
> Jaap Spies wrote:
Hi Jaap,
> > --
>
> > The following tests failed:
>
> > sage -t pha2/devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py
> > # 1 doctests failed
> >
Jaap Spies wrote:
>
> --
>
> The following tests failed:
>
> sage -t
> pha2/devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctests
> failed
> --
mabshoff wrote:
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very solid.
>
> Unfortunately there w
34 matches
Mail list logo
