We've released Sage 4.5.3.alpha2.
Source archive:
http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2.tar
Upgrade path:
http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2/
The long doctests pass for me on bsd, redhawk, sage, and
t2.math.washington.edu.
Please build, test, and report! We'd love to hear about your
experiences with this release.
The 4.5.3 series is still in feature freeze and blocker squeeze.
== Tickets ==
Closed tickets:
#7708: Harald Schilly: upgrade openopt spkg to 0.29 [Reviewed by Harald
Schilly]
Merged in sage-4.5.3.alpha2:
#9689: David Kirkby: Numerical noise on
devel/sage-main/sage/symbolic/expression.pyx computing sinh(1) [Reviewed
by John Cremona]
#9693: David Kirkby: Maxima is printing asinh(1.0) without a leading
zero (.8813735870195429) on Solaris 10 x86 [Reviewed by John Cremona]
#9703: David Kirkby: Doctest failures caused by non-working sympow on
32-bit Solaris x86 and 32-bit OpenSolaris [Reviewed by Jeroen Demeyer,
Mitesh Patel, Carl Witty]
#9722: Leif Leonhardy: PARI/GP build error on Fedora 13 [Reviewed by
Jeroen Demeyer, Mitesh Patel]
#9735: John Palmieri: Numerical noise on sage/stats/hmm/chmm.pyx on both
Solaris x86 and OpenSolaris x86 [Reviewed by David Kirkby]
#9760: John Palmieri: Possible numerical noise doctest failure in
sage/matrix/matrix2.pyx on t2 [Reviewed by David Kirkby]
#9761: David Kirkby: Adjust spkg/standard/deps to build Python before
zn_poly, and make two other dependencies explicit [Reviewed by Leif
Leonhardy]
#9765: John Palmieri: matrix2.pyx: replace "x < 1e-15" by "abs(x) <
1e-15" [Reviewed by Mitesh Patel]
Upgraded from 4.5.1 (I think) and passed long tests on
[aghitza@soleil sage-4.5.1]$ uname -a
Linux soleil.ms.unimelb.edu.au 2.6.18-194.11.1.el5 #1 SMP Tue Jul 27 05:45:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Best,
Alex
--
Alex Ghitza -- http://aghitza.org/
Lecturer in Mathematics -- The University of Melbourne -- Australia
Ubuntu 9.04 x86_64 (Core2, gcc 4.5.0, native code, O3):
make build: OK (parallel build from scratch, 32 jobs)
make doc: OK
make ptestlong: OK (all tests passed; 4 threads)
Fedora 13 x86_64 (Core2, gcc 4.4.4, native code, O3):
make build: OK (parallel build from scratch, 32 jobs)
make doc: OK
make ptestlong: OK (all tests passed; 4 threads)
Ubuntu 9.04 x86 (Pentium 4 Prescott, gcc 4.3.3, native code):
make build: OK (parallel build from scratch, 6 jobs)
make doc: OK
make ptestlong: OK (all tests passed; 2 threads)
-Leif
We need to sort out these test that fail with zero failures, like the
first two you list do.
Dave
> Hi there,
>
> We've released Sage 4.5.3.alpha2.
>
> Source archive:
>
> http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2.tar
>
> Upgrade path:
>
> http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2/
Upgraded from 4.5.3.a1, w/o problems. Ran 'ptestlong', and one test
failed. Failure noted below. I reran the test by hand and it
passed. Mac OS X, 10.5.8, Dual Quad Xeon.
Justin
sage -t -long devel/sage/sage/interfaces/psage.py
**********************************************************************
File "/Users/Sage/sage-4.5.3.alpha1/devel/sage-main/sage/interfaces/
psage.py", l
ine 35:
sage: print "ignore this"; w # random output
Exception raised:
Traceback (most recent call last):
File "/Users/Sage/sage-4.5.3.alpha1/local/bin/ncadoctest.py",
line 1231, i
n run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/Users/Sage/sage-4.5.3.alpha1/local/bin/sagedoctest.py",
line 38, in
run_one_example
OrigDocTestRunner.run_one_example(self, test, example,
filename, compile
flags)
File "/Users/Sage/sage-4.5.3.alpha1/local/bin/ncadoctest.py",
line 1172, i
n run_one_example
compileflags, 1) in test.globs
File "<doctest __main__.example_0[5]>", line 1, in <module>
print "ignore this"; w # random output###line 35:
sage: print "ignore this"; w # random output
File "/Users/Sage/sage-4.5.3.alpha1/local/lib/python/site-
packages/sage/mi
sc/displayhook.py", line 174, in displayhook
print_obj(sys.stdout, obj)
File "/Users/Sage/sage-4.5.3.alpha1/local/lib/python/site-
packages/sage/mi
sc/displayhook.py", line 142, in print_obj
print >>out_stream, `obj`
File "/Users/Sage/sage-4.5.3.alpha1/local/lib/python/site-
packages/sage/in
terfaces/expect.py", line 1670, in __repr__
s = s.replace(self._name, self.__dict__['__custom_name'])
KeyError: '__custom_name'
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
I'm beginning to like the cut of his jibberish.
-----------
Can you think of any reason the test might have failed first time? Do your logs
show a lack or swap space, disk I/O error, or something else that might explain
why it failed first time, but passed when you re-run it?
I find this a bit worrying, as we don't know if Sage is getting things wrong
occasionally, or the doctest framework is broken. But this seems quite a common
problem, with tests failing in ptestlong but passing individually.
What I don't know for sure is if testlong is more reliable. I think it might be.
Dave
The only things of note in the logs during the time of the tests were
three crashes, 2 in maxima, one in genus2reduction. Not sure how to
tie the psage failure to one of those. It looks like there is perhaps
a problem related to string matching, if I understand the traceback.
I know squat about this stuff, so I can only speculate wildly and
inaccurately.
The '__custom_name' key is checked by hasattr() before being
referenced in the line that blows up (with a KeyError exception).
That seems quite odd to me.
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
Experience is what you get
when you don't get what you want.
--------
Could you give a link to the ptestlong log?
It seems that R's lattice package wasn't compiled or installed on your
system. Could you confirm this by rerunning the test and checking the
output of
$ cd SAGE_ROOT
$ ./sage -R
[...]
> installed.packages()
? On bsd (OS X 10.6) and sage.math (Ubuntu 8.04.4 LTS), this gives
information for 27 packages:
base
boot
class
cluster
codetools
datasets
foreign
graphics
grDevices
grid
KernSmooth
lattice
MASS
Matrix
methods
mgcv
nlme
nnet
rpart
spatial
splines
stats
stats4
survival
tcltk
tools
utils
On t2.math (Solaris 10), I get data for 20 packages:
base
boot
cluster
codetools
datasets
foreign
graphics
grDevices
grid
KernSmooth
lattice
MASS
methods
nlme
splines
stats
stats4
tcltk
tools
utils
This is a known problem on t2, at least:
> On 08/24/2010 08:29 PM, Justin C. Walker wrote:
>> On Aug 24, 2010, at 17:14 , Dr. David Kirkby wrote:
>>> On 08/24/10 07:29 PM, Justin C. Walker wrote:
[snip]
>> The '__custom_name' key is checked by hasattr() before being
>> referenced
>> in the line that blows up (with a KeyError exception). That seems
>> quite
>> odd to me.
>
> Could you give a link to the ptestlong log?
The log is at
sage.math.washington.edu:~justin/logs/4.5.3.a2.log
Justin
--
Justin C. Walker
Curmudgeon-at-large
--
Network, n., Difference between work
charged for and work done
Jeroen.
The PSage interface spawns multiple parallel, non-blocking copies of the
Sage interpreter. The problem *might* be a race condition within
psage.py itself that the doctest occasionally exposes.
> **********************************************************************
> File
> "/Users/Sage/sage-4.5.3.alpha1/devel/sage-main/sage/interfaces/psage.py", l
Justin also wrote:
> The '__custom_name' key is checked by hasattr() before being referenced
> in the line that blows up (with a KeyError exception). That seems quite
> odd to me.
From sage.interfaces.expect.ExpectElement:
def __repr__(self):
self._check_valid()
try:
if self._get_using_file:
s = self.parent().get_using_file(self._name)
except AttributeError:
s = self.parent().get(self._name)
if s.__contains__(self._name):
if hasattr(self, '__custom_name'):
s = s.replace(self._name, self.__dict__['__custom_name'])
return s
Does anyone have an example for which the replace statement is executed?
Is is possible that Sage's R is reading a system-wide/personal R
configuration file with these paths?
For reference, on {bsd,sage,t2}.math I see
$ sage -R
R version 2.10.1 (2009-12-14)
Copyright (C) 2009 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
>
> On 08/24/2010 01:29 PM, Justin C. Walker wrote:
>> Upgraded from 4.5.3.a1, w/o problems. Ran 'ptestlong', and one test
>> failed. Failure noted below. I reran the test by hand and it
>> passed.
>> Mac OS X, 10.5.8, Dual Quad Xeon.
>>
>> sage -t -long devel/sage/sage/interfaces/psage.py
>
>
> The PSage interface spawns multiple parallel, non-blocking copies of
> the
> Sage interpreter. The problem *might* be a race condition within
> psage.py itself that the doctest occasionally exposes.
Someone who knows what's going on in this code will have to speak up.
I would expect the code here to be executed for each
"thread" (although I think that's not exactly what's going on under
the covers). Isn't 'self' a single instance of something or other
(pardon my drifting into technical speak)?
> Justin also wrote:
>> The '__custom_name' key is checked by hasattr() before being
>> referenced
>> in the line that blows up (with a KeyError exception). That seems
>> quite
>> odd to me.
>
>
> From sage.interfaces.expect.ExpectElement:
>
> def __repr__(self):
> self._check_valid()
> try:
> if self._get_using_file:
> s = self.parent().get_using_file(self._name)
> except AttributeError:
> s = self.parent().get(self._name)
> if s.__contains__(self._name):
> if hasattr(self, '__custom_name'):
> s = s.replace(self._name,
> self.__dict__['__custom_name'])
> return s
>
> Does anyone have an example for which the replace statement is
> executed?
Isn't the blow-up an instance of the statement being executed? Am I
missing your point?
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------
Hi there,
We've released Sage 4.5.3.alpha2.
Source archive:
http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2.tar
Upgrade path:
http://sage.math.washington.edu/home/release/sage-4.5.3.alpha2/sage-4.5.3.alpha2/
The long doctests pass for me on bsd, redhawk, sage, and
t2.math.washington.edu.
Please build, test, and report! We'd love to hear about your
experiences with this release.
The 4.5.3 series is still in feature freeze and blocker squeeze.
== Tickets ==
Closed tickets:
#7708: Harald Schilly: upgrade openopt spkg to 0.29 [Reviewed by Harald
Schilly]
Merged in sage-4.5.3.alpha2:
#9689: David Kirkby: Numerical noise on
devel/sage-main/sage/symbolic/expression.pyx computing sinh(1) [Reviewed
by John Cremona]
#9693: David Kirkby: Maxima is printing asinh(1.0) without a leading
zero (.8813735870195429) on Solaris 10 x86 [Reviewed by John Cremona]
#9703: David Kirkby: Doctest failures caused by non-working sympow on
32-bit Solaris x86 and 32-bit OpenSolaris [Reviewed by Jeroen Demeyer,
Mitesh Patel, Carl Witty]
#9722: Leif Leonhardy: PARI/GP build error on Fedora 13 [Reviewed by
Jeroen Demeyer, Mitesh Patel]
#9735: John Palmieri: Numerical noise on sage/stats/hmm/chmm.pyx on both
Solaris x86 and OpenSolaris x86 [Reviewed by David Kirkby]
#9760: John Palmieri: Possible numerical noise doctest failure in
sage/matrix/matrix2.pyx on t2 [Reviewed by David Kirkby]
#9761: David Kirkby: Adjust spkg/standard/deps to build Python before
zn_poly, and make two other dependencies explicit [Reviewed by Leif
Leonhardy]
#9765: John Palmieri: matrix2.pyx: replace "x < 1e-15" by "abs(x) <
1e-15" [Reviewed by Mitesh Patel]
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To post to this group, send email to sage-r...@googlegroups.com.
To unsubscribe from this group, send email to sage-release...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
Does the problem recur if you try again with 'notebook()' or use
'notebook(open_viewer=False)' and manually browse to http://localhost:8000 ?
Ubuntu 10.04 LTS x86_64 (Core2, gcc 4.4.3, native code, O3):
make build: OK (parallel build from scratch, 32 jobs)
make doc: OK
make ptestlong: OK (all tests passed; 4 threads)
Fedora 13 x86 (Pentium 4 Prescott, gcc 4.4.4, native code, O3):
It appears to be a KDE configuration problem. Which Linux distribution
and version are you running? Perhaps someone who runs Sage on the same
or a similar distribution can provide additional data? Unfortunately, I
don't have access to a machine with both Sage and KDE.
Another workaround is to
export SAGE_BROWSER="/usr/bin/firefox"
say, before starting Sage.
Another example:
export SAGE_BROWSER='~/bin/Sage_browser'
where Sage_browser is an executable script that contains
#!/bin/bash
/usr/bin/firefox -P myprofile -remote "openURL($*, new-tab)"
This should open the requested page in a new tab in an already running
Firefox profile called myprofile.
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To post to this group, send email to sage-r...@googlegroups.com.
> To unsubscribe from this group, send email to sage-release...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
>
>
--
Tim Joseph Dumol <tim (at) timdumol (dot) com>
http://timdumol.com
Proxy answer:
[K]Ubuntu 10.04 LTS amd64 (x86_64, i.e. 64-bit).
-Leif
I should have been clearer. I'm looking for other, working examples
with which to experiment and to write doctests for
ExpectElement.__repr__. With
if s.__contains__(self._name):
print 'FOOO self._name', self._name
if hasattr(self, '__custom_name'):
print 'FOOO self.__custom_name', self.__custom_name
s = s.replace(self._name, self.__dict__['__custom_name'])
the long doctests still pass for me on sage.math.
Also, I ran
./sage -t -long devel/sage/sage/interfaces/psage.py
serially 1000 times in each of 20 copies of 4.5.3.alpha1, each with its
own DOT_SAGE directory. There were 17 failures, all the same as on your
system, out of 20000 total runs.
This appears to rule out the Sage parallel doctester
SAGE_LOCAL/bin/sage-ptest as the source of the problem.
I'm now batch-testing a .sage file that contains just the psage.py example
v = [PSage() for _ in range(3)]
w = [x('factor(2^%s-1)'% randint(250,310)) for x in v]
w # random output (depends on timing)
w # random output
Another workaround is to
export SAGE_BROWSER="/usr/bin/firefox"
say, before starting Sage.
Another example:
export SAGE_BROWSER='~/bin/Sage_browser'
where Sage_browser is an executable script that contains
#!/bin/bash
/usr/bin/firefox -P myprofile -remote "openURL($*, new-tab)"
This should open the requested page in a new tab in an already running
Firefox profile called myprofile.