Helloooooo everybody !!
I finally found out where my bug from [1] was coming from !
It seems to come from the fact that I installed Sage in the directory
$HOME/.Sage/. And Sage does not like that. Actually, it refuses to test any
file whose path contains "/." and so of course thinks that there is nothing
to test when I type :
sage -tp 5 /home/ncohen/.Sage/devel/sage-2/sage
The error message does not say that there is nothing to test, but instead
that there are not enough processors available.... This comes from line 441
of local/bin/sage-ptest
sage-ptest:441: numthreads = min(numthreads, len(files)) # don't use
more threads than files
And the line that filters files whose path contains "/." lies in the "skip"
function of sage-ptest :
def skip(F):
"""
Returns true if the file should not be tested
"""
.........
if (filenm[0] == '.' or (os.path.sep + '.' in G.lstrip(os.path.sep
+ '.'))
or 'nodoctest' in open(G).read()[:50]):
Considering what SAGE_ROOT is on my computer, all my files match the
(os.path.sep + '.' in G.lstrip(os.path.sep + '.')) test :-)
Hoping that somebody who knows how this all works will find some sense in
this (bug?) report,
Noyeux Joel !
Nathann
[1]
https://groups.google.com/forum/?fromgroups=#!topic/sage-support/UmDkDuYh8C8
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
