On 09/21/10 01:07 AM, Dan Drake wrote:
On Mon, 20 Sep 2010 at 09:04AM -0700, John H Palmieri wrote:
Should we change the spkg-check file for the python spkg? Are there
*any* machines on which it passes? I've tried vanilla python-2.6.6
and python-2.7, and while I can get python-2.7 to pass self-tests on
one machine (sage.math), it fails on every other machine I've tried: a
Mac OS X 10.6 machine, t2.math, and a handful of skynet machines. I
think python-2.6.6 fails on all of these, including sage.math.
I have the same problem, and I also would really like a build with
SAGE_CHECK=yes to succeed. Perhaps we should work with Python upstream
on this; they might fix bugs, fix tests, or give us suggestions for
workarounds.
Dan
My experience has been less than good in this matter. I actually submitted a
patch for a Solaris bug fix. I was told integrating it would be on someone's
TODO list, but he could not guarantee it would be done within the next year. He
offered me a 5:1 swap. I had to review 5 patches, and if I did he would
integrate my one. The problem was my Python skills are not good, so there was
not much I could do about that.
I guess it depends on who you manage to interest in the bug. Get the right
person and you might have more luck than what I did.
There are a number of Python tests failing tests, and they seem to vary by the
nature of individuals computers.
I think the most sensible option is to have an environment variable where we can
run SAGE_CHECK=yes, but ignore specific packages. Not only would that have uses
where packages are known to fail, but when the tests take a long time and people
chose not to run them.
dave
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
