On Nov 19, 11:23 am, Volker Braun wrote:
> I propose that we just add a doctest that makes it clear that you shouldn't
> run doctests as root. No more mysterious failures.
>
> sage: import os
> sage: try:
> ... uid = os.getuid()
> ... except AttributeError:
> ... uid =
On Sat, Nov 19, 2011 at 5:22 AM, Jeroen Demeyer wrote:
> On 2011-11-19 12:23, Volker Braun wrote:
>> I propose that we just add a doctest that makes it clear that you
>> shouldn't run doctests as root. No more mysterious failures.
> Well, I certainly agree that running doctests as root is not very
On Saturday, November 19, 2011 1:22:09 PM UTC, Jeroen Demeyer wrote:
>
> Well, I certainly agree that running doctests as root is not very
> clever, I don't think we should *prevent* anyone from doing that.
My suggestion wouldn't prevent anyone from running the doctest as root,
they'd just get a
On 2011-11-19 12:23, Volker Braun wrote:
> I propose that we just add a doctest that makes it clear that you
> shouldn't run doctests as root. No more mysterious failures.
Well, I certainly agree that running doctests as root is not very
clever, I don't think we should *prevent* anyone from doing t
Why not put it in the doctester module itself? That way you'll avoid
actually running any doctests as root. If you make it just a doctest in the
suite, it will fail, but all the doctests will be run as root anyway.
-Keshav
Join us in #sagemath on irc.freenode.net !
--
To post to this gro
Since there is apparently only one doctests that fails with elevated
privileges I'd put it right there, at the place where it fails.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
Fo
Volker Braun wrote:
> I propose that we just add a doctest that makes it clear that you shouldn't
> run doctests as root. No more mysterious failures.
>
> sage: import os
> sage: try:
> ...uid = os.getuid()
> ... except AttributeError:
> ...uid = -1
> sage: if uid=
I propose that we just add a doctest that makes it clear that you shouldn't
run doctests as root. No more mysterious failures.
sage: import os
sage: try:
...uid = os.getuid()
... except AttributeError:
...uid = -1
sage: if uid==0:
... raise OSErr
Nathann Cohen wrote:
> Yoo !!!
>
> > doctest failure in linear_programming.rst:
> > http://trac.sagemath.org/sage_trac/ticket/12019
> This ticket is now waiting for a review.
> > failing doctest in integer_vector.py (gale ryser theorem)
> > http://trac.sagemath.org/sage_trac/ticket/12022
>
Yoo !!!
> doctest failure in linear_programming.rst:
> http://trac.sagemath.org/sage_trac/ticket/12019
This ticket is now waiting for a review.
> failing doctest in integer_vector.py (gale ryser theorem)
> http://trac.sagemath.org/sage_trac/ticket/12022
Same here. And these tickets coul
About the failing test
sage -t -force_lib "devel/sage/sage/graphs/digraph.py" # Killed/
crashed
I ran the test again with -verbose
I think its connected to the routine dcycle.feedback_edge_set (in line
1252) and maybe its an integer / floating error
Trying:
cycle.size()###line 1338:_sage_
> We should change the doctest to execute "rm -rf /" instead. This will also
> provide a valuable lesson for people that use privileged accounts for
> everything :-)
Not to mention that all free softwares are distributed with the
warning "You use this code at your own risk" and that we never had
On Sunday, November 13, 2011 3:05:32 PM UTC+1, Emil Widmann wrote:
>
> I checked that the directory was created and the permissions were set
> to correctly.
> Is this critical or can it be fixed with some sort of setting?
>
> EDIT: I found the culprit - I ran doctest as root.
> If I run th
> Anything that makes the doctests scream qualifies as a bug. Anything
> that is not even a bug but that is not the behaviour you expected also
> qualifies as a bug, even though it may just mean rewriting some
> documentation :-)
Ok I created some tickets:
doctest failure in linear_programming.rst
Hello !!
> seriously. But to go into the details with each failing test takes
> time and is tedious, so I think it is better to avoid possible
> problems (like those with the multible solutions) whenever possible.
Yepyep. All that needs to be fixed :-)
> I fully agree - is it okay if I crea
On Nov 13, 4:53 pm, Nathann Cohen wrote:
> Helloo Emil !
>
> Well, it looks like I am to blame for most of these errors :-/
Hi Nathan, thanks for quick response!
I am not sure if those are errors, but when I, as a non export, try to
build sage then I take failing doctests
seriously
Helloo Emil !
Well, it looks like I am to blame for most of these errors :-/
The first one is about a matching in Petersen's Graph. Then the error in
the gale_ryser theorem function. Both codes are calling GLPK (I assume that
you have not installed the CBC package ? Or CPLEX ?), and
17 matches
Mail list logo
