#8059: update Singular SPKG to newest upstream release
----------------------------------------------------------------------+-----
Reporter: malb |
Owner:
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-4.5.2
Component: packages |
Keywords:
Author: Martin Albrecht |
Upstream: Reported upstream. Little or no feedback.
Reviewer: David Kirkby, Simon King, William Stein, John Palmieri |
Merged:
Work_issues: rebase patch |
----------------------------------------------------------------------+-----
Changes (by SimonKing):
* reviewer: David Kirkby => David Kirkby, Simon King, William Stein,
John Palmieri
* work_issues: => rebase patch
Comment:
Replying to [comment:98 SimonKing]:
> Replying to [comment:97 jhpalmieri]:
> > These messages ("File not found") are more or less typical when the
doctests time out. ... If you really want to try again, try {{{export
SAGE_TIMEOUT_LONG=6000}}}
>
> OK, doing it now.
Again, the setting is: Sage 4.5.1 plus singular-3-1-1-4.patch plus
singular-3-1-1-4.spkg. {{{sage -ptestlong}}} on t2 with {{{export
SAGE_TIMEOUT_LONG=6000}}} results in exactly one doctest failure:
{{{
sage -t -long devel/sage/sage/parallel/decorate.py
**********************************************************************
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-SunOS/devel/sage-
main/sag
e/parallel/decorate.py", line 152:
sage: v = list(f([1,2,4])); v.sort(); v
Exception raised:
Traceback (most recent call last):
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/bin/nca
doctest.py", line 1231, in run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/bin/sag
edoctest.py", line 38, in run_one_example
OrigDocTestRunner.run_one_example(self, test, example, filename,
compile
flags)
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/bin/nca
doctest.py", line 1172, in run_one_example
compileflags, 1) in test.globs
File "<doctest __main__.example_4[9]>", line 1, in <module>
v = list(f([Integer(1),Integer(2),Integer(4)])); v.sort();
v###line 152:
sage: v = list(f([1,2,4])); v.sort(); v
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/lib/pyt
hon/site-packages/sage/parallel/multiprocessing_sage.py", line 64, in
parallel_i
ter
p = Pool(processes)
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/lib/pyt
hon2.6/multiprocessing/__init__.py", line 227, in Pool
return Pool(processes, initializer, initargs)
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/lib/pyt
hon2.6/multiprocessing/pool.py", line 104, in __init__
w.start()
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/lib/pyt
hon2.6/multiprocessing/process.py", line 104, in start
self._popen = Popen(self)
File "/scratch/sking/sage-4.5.1-Solaris_10_SPARC-sun4u-
SunOS/local/lib/pyt
hon2.6/multiprocessing/forking.py", line 94, in __init__
self.pid = os.fork()
OSError: [Errno 12] Not enough space
**********************************************************************
1 items had failures:
1 of 12 in __main__.example_4
***Test Failed*** 1 failures.
For whitespace errors, see the file
/home/SimonKing/.sage//tmp/.doctest_decorate
.py
[46.5 s]
}}}
So, not enough space. Does that mean the hard disc (or at least
{{{/scratch}}} or my home directory) is too full?
Anyway, I repeated the failing test separately, and then it succeeded:
{{{
sage subshell$ sage -t -long devel/sage/sage/parallel/decorate.py
sage -t -long "devel/sage/sage/parallel/decorate.py"
[48.8 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 48.8 seconds
}}}
So, can one say that all tests pass on t2?
Looking at the previous posts, it seems that the status is:
- "builds and passes all tests with sage-4.5" on sage.math (William)
- "All tests pass on bsd.math" (Martin)
- "Amazingly, this fully works on Cygwin!!" (William)
- With a little effort (extending timeout and running one test
separately) all tests of sage-4.5.1+patch+spkg pass on t2.
- "the patch doesn't apply cleanly to Sage 4.5.2.alpha0" (John).
Do you agree that this is a positive review '''once the patch is
rebased''', and that William, John and myself should be added to the list
of referees?
Cheers,
Simon
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8059#comment:100>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
