[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-22 Thread William Stein
On Mon, Jun 22, 2009 at 7:29 PM, Justin C. Walker wrote: > > > On Jun 18, 2009, at 10:26 , Craig Citro wrote: > >> >> Hi all, >> >> Here's rc3, which *should* be the last rc for this release cycle. I've >> tested it on my laptop and the build farm, and I've had no troubles at >> all, and it's curr

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-22 Thread Justin C. Walker
On Jun 18, 2009, at 10:26 , Craig Citro wrote: > > Hi all, > > Here's rc3, which *should* be the last rc for this release cycle. I've > tested it on my laptop and the build farm, and I've had no troubles at > all, and it's currently going on a few other machines, so hopefully > that'll turn out

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-22 Thread gsw
Hi Craig, On 21 Jun., 23:32, Craig Citro wrote: > Hi Georg, > > > The root cause was the patch for trac #2513 which was incorporated in > > Sage-4.0.2.alpha4, concerning the setting (or not ...) of the variable > > LANG in the sage-env script. > > > I'll prepare a nice patch with some explanatio

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-21 Thread Craig Citro
Hi Georg, > The root cause was the patch for trac #2513 which was incorporated in > Sage-4.0.2.alpha4, concerning the setting (or not ...) of the variable > LANG in the sage-env script. > > I'll prepare a nice patch with some explanations for the R.spkg's > "spkg-install" script to use 'LANG="en_

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-21 Thread gsw
On 19 Jun., 08:28, gsw wrote: > > I checked back for the my Sage-4.0.1 Intel Mac OS X 10.4 build and > > unfortunately yes, this problem is there, too --- so the currently > > bdist'ed version is flawed :-/ > > I don't seem to have my Sage-4.0 logs anymore, but I found those for > > Sage-3.4.2,

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-20 Thread John Cremona
2009/6/20 Craig Citro : > >>> Interesting ... that means that the call to sys.exit(0) is generating >>> an exception that's getting caught in the except: clause. Can you file >>> a ticket for this? I'll happily review it. :) >> >> I created a ticket #6364, without a patch though since it's outside

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-20 Thread Craig Citro
>> Interesting ... that means that the call to sys.exit(0) is generating >> an exception that's getting caught in the except: clause. Can you file >> a ticket for this? I'll happily review it. :) > > I created a ticket #6364, without a patch though since it's outside > SAGE_ROOT/devel. > Actually

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-20 Thread John Cremona
2009/6/20 Craig Citro : > >> That did the trick -- ran fine and no "failure" line at the end.  (I >> moved that line to the end as suggested) >> > > Interesting ... that means that the call to sys.exit(0) is generating > an exception that's getting caught in the except: clause. Can you file > a ti

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread Craig Citro
> That did the trick -- ran fine and no "failure" line at the end.  (I > moved that line to the end as suggested) > Interesting ... that means that the call to sys.exit(0) is generating an exception that's getting caught in the except: clause. Can you file a ticket for this? I'll happily review i

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread John Cremona
2009/6/19 Craig Citro : > >> All seemed well with that test (all etsts passed, etc), but the final >> lines of output are >> >> All tests passed! Popping patches from queue ... >> cd "/home/jec/sage-4.0.2/devel/sage" && hg qpop -a >> cd "/home/jec/sage-4.0.2/devel/sage" && hg qdelete trac_5307.pat

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread John Cremona
2009/6/19 Craig Citro : > >>> Similar error with any other sage -merge command.  Am I doing >>> something wrong? >> >> I think I had this problem based on the current directory.  Could you >> try in a different directory?  (I think this is a sage-wide problem >> but I can't say with certainty.) >>

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread Craig Citro
>> Similar error with any other sage -merge command.  Am I doing >> something wrong? > > I think I had this problem based on the current directory.  Could you > try in a different directory?  (I think this is a sage-wide problem > but I can't say with certainty.) > Yep, I remember Nick saying som

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread Craig Citro
> All seemed well with that test (all etsts passed, etc), but the final > lines of output are > > All tests passed! Popping patches from queue ... > cd "/home/jec/sage-4.0.2/devel/sage" && hg qpop -a > cd "/home/jec/sage-4.0.2/devel/sage" && hg qdelete trac_5307.patch > Building failed with System

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread John Cremona
2009/6/19 Nick Alexander : > >> I wanted to try out this feature. Here is what happened. I built >> 4.0.2.rc3 from scratch, made a clone called test, cd'd into >> devel/sage-test, initialised MQ by "sage -hg qinit". And then: >> >> j...@host-57-89%sage -merge -c >> Traceback (most recent call l

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread Nick Alexander
> I wanted to try out this feature. Here is what happened. I built > 4.0.2.rc3 from scratch, made a clone called test, cd'd into > devel/sage-test, initialised MQ by "sage -hg qinit". And then: > > j...@host-57-89%sage -merge -c > Traceback (most recent call last): > File "/home/jec/sage-curre

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread John Cremona
2009/6/18 Craig Citro : > > Hi all, > > Here's rc3, which *should* be the last rc for this release cycle. I've > tested it on my laptop and the build farm, and I've had no troubles at > all, and it's currently going on a few other machines, so hopefully > that'll turn out fine, too. Please test it

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread William Stein
On Fri, Jun 19, 2009 at 1:13 PM, gsw wrote: > > > > On 19 Jun., 08:50, Craig Citro wrote: >> > Yes, the parallel build code was reworked for 4.0.1.  Not sure why >> > we're seeing this, but still. >> >> Well, the parallel build code in 4.0.1 *should* be contained to the >> sage build itself (it'

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-19 Thread gsw
On 19 Jun., 08:50, Craig Citro wrote: > > Yes, the parallel build code was reworked for 4.0.1.  Not sure why > > we're seeing this, but still. > > Well, the parallel build code in 4.0.1 *should* be contained to the > sage build itself (it's in sage's setup.py, and it's a separate > builder that

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Craig Citro
> Yes, the parallel build code was reworked for 4.0.1.  Not sure why > we're seeing this, but still. > Well, the parallel build code in 4.0.1 *should* be contained to the sage build itself (it's in sage's setup.py, and it's a separate builder that one has to instantiate). I won't say it's impossi

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Nick Alexander
On 18-Jun-09, at 11:28 PM, gsw wrote: > > > > On 19 Jun., 08:21, gsw wrote: >> Hi, >> >> r/rpy does not build reliably for me anymore using " export >> MAKE='make >> -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this >> already for Sage-4.0.2.rc0 (in a one-message thread :-) )

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread gsw
On 19 Jun., 08:21, gsw wrote: > Hi, > > r/rpy does not build reliably for me anymore using " export MAKE='make > -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this > already for Sage-4.0.2.rc0 (in a one-message thread :-) ) thinking > that it would be sporadic, but it seems to h

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread gsw
Hi, r/rpy does not build reliably for me anymore using " export MAKE='make -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this already for Sage-4.0.2.rc0 (in a one-message thread :-) ) thinking that it would be sporadic, but it seems to hit always now: I built Sage-4.0.2.rc2 and Sa

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Craig Citro
> All tests passed on 64-bit Ubuntu 9.04 and 32-bit Fedora 10. All tests > passed on bsd.math, except that #6242 is still a problem; the > birds_other.rst doctests segfault between a quarter and a third of the > time. > Yep, this is a known issue. This is the same as #6304, which David Harvey had

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Dan Drake
All tests passed on 64-bit Ubuntu 9.04 and 32-bit Fedora 10. All tests passed on bsd.math, except that #6242 is still a problem; the birds_other.rst doctests segfault between a quarter and a third of the time. Dan -- --- Dan Drake - KAIST Department of Mathematical Sciences --- http:

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread David Joyner
compiled fine and all tests passed on amd64 ubuntu 9.04. On Thu, Jun 18, 2009 at 1:26 PM, Craig Citro wrote: > > Hi all, > > Here's rc3, which *should* be the last rc for this release cycle. I've > tested it on my laptop and the build farm, and I've had no troubles at > all, and it's currently

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread John Cremona
All tests passed on a fresh build on ubuntu 32-bit (took no longer than usual: 3099s). Same on 64-bit (<3000s). John 2009/6/18 Marshall Hampton : > > All tests passed on an intel mac pro running 10.4.11. > > The tests took 6975 seconds, which seems like a big increase from > 3.0.2 (4818 seconds

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Marshall Hampton
All tests passed on an intel mac pro running 10.4.11. The tests took 6975 seconds, which seems like a big increase from 3.0.2 (4818 seconds) and 3.4 (5358 seconds). Is this simply because of the additional doctests, or are there serious speed regressions somewhere? I recall some discussion abou

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Jaap Spies
Jaap Spies wrote: > Craig Citro wrote: >> Hi all, >> >> Here's rc3, which *should* be the last rc for this release cycle. I've >> tested it on my laptop and the build farm, and I've had no troubles at >> all, and it's currently going on a few other machines, so hopefully >> that'll turn out fine,

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread John H Palmieri
On Jun 18, 12:17 pm, Jaap Spies wrote: > Craig Citro wrote: > > Hi all, > > > Here's rc3, which *should* be the last rc for this release cycle. I've > > tested it on my laptop and the build farm, and I've had no troubles at > > all, and it's currently going on a few other machines, so hopefully >

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Jaap Spies
Craig Citro wrote: > Hi all, > > Here's rc3, which *should* be the last rc for this release cycle. I've > tested it on my laptop and the build farm, and I've had no troubles at > all, and it's currently going on a few other machines, so hopefully > that'll turn out fine, too. Please test it and l

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-18 Thread Minh Nguyen
On Fri, Jun 19, 2009 at 3:26 AM, Craig Citro wrote: > > I believe that the necessary upgrade bits are sitting here, but I > haven't tried it: > > http://sage.math.washington.edu/home/craigcitro/release/sage-4.0.2.rc3/ Upgraded from sage-4.0.2.rc3 OK on sage.math. But soon after executing the